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

[Thomas Lamprecht <t.lamprecht@proxmox.com>]

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.



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel