On 11/4/24 4:46 PM, Martin Rys wrote:
This isn't about the AUR but about pkgctlI have done the same exact mistake of archweb vs aurweb
:)
As such, I don't think a warning for packages that "lack" this makes much sense.Hm, maybe a good addition for namcap though?
Such a warning may be added to `pkgctl` directly, see [1] and [2].
Just to make things clear, this isn't about automating the process of flagging packages out of date on the AURI see, so currently official repositories are autoflagged if they have nvchecker, but AUR repositories aren't?
No they are not. The presence of the .nvchecker.toml file currently only allows package maintainers to run `pkgctl version check` / `pkgctl version upgrade` for the package, nothing more.
A PoC [3] has started to autoflag official repositories packages thanks to this nvchecker integration but this is a currently a WIP and it is separate from `pkgctl` itself.
Would it be reasonable to extend it to AUR too? I would love it for my packages.
I'm not an AURWeb developer so I can't say how feasible that would be, but seing the problematic we are eventually facing with the above PoC in terms of resource loads and API limit rates implied by the monitoring of the ~14k packages of the official repository, I doubt that porting this to the ~94K AUR packages is doable.
Martin
[1] https://gitlab.archlinux.org/archlinux/devtools/-/issues/236 [2] https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/275 [3] https://gitlab.archlinux.org/archlinux/nvchecker-poc -- Regards, Robin Candau / Antiz
Attachment:
OpenPGP_0xFDC3040B92ACA748.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature
