[pve-devel] [PATCH pve_flutter_frontend] Updated Gradle version and some build dependencies.

[Alexander Abraham]

Hi,

thank you for explaining this to me. I will make sure I set this up.

I did read the link that Shannon sent and of course, understood the difference upon reading it. I wasn't quite sure which to use as the poster used the kts variety and we are using the Groovy variety. Now I know and I'm clear about which is for which.

Best,
Alexander


> Thomas Lamprecht <t.lamprecht at proxmox.com> hat am 03.03.2025 10:50 CET geschrieben:
> 
>  
> Am 03.03.25 um 10:38 schrieb Alexander Abraham:
> > Keeping up with all the emails coming in is something I still need to get on top of.
> 
> I'd recommend setting up mail filter to move all mails that stem from a mailing list,
> i.e. have the List-Id header set, to a dedicated folder for that list. Most filter
> solution, including our company mail here, have dedicated criteria to match list mails.
> Fir pve-devel you would use then e.g. the following value to match on:
> "Proxmox VE development discussion <pve-devel.lists.proxmox.com>"
> 
> 
> That the list mails go into a separate folder leaving your inbox less cluttered and
> giving more attention to mails where you are explicitly in the "To" or "Cc" list, as
> such mails are directly delivered (not through the list) and thus won't match such a
> mailing-list filter, ensuring you will get them in your (now less crowded) inbox.
> 
> 
> > For them, specifying the namespace was the missing piece for getting the build to work.
> 
> That itself is fine, Shannon just wondered why you use an assignment like `namespace = "..."`
> here over the `namespace "..."` (note the missing `=`). As the former is for gradle build
> scripts in the kotlin script (kts) language, a newer variant to configure gradle builds,
> whereas the latter variant without the equal sign is for the older gradle native groovy
> language that we currently use here.