On 1/21/24 22:19, Daurnimator wrote:
There's not really any ongoing discussions.
For what it's worth, my personal motivation is to package qubes guest
packages into the Arch [extra] repo, of which qubes-libvchan will
depend on shared library from xen
(https://github.com/QubesOS/qubes-core-
On 22/1/24 16:59, Sam Mulvey wrote:
Hello!
I've been maintaining xen and associated packages for a few years. This
relative evening the package got the following comment:
https://aur.archlinux.org/pkgbase/xen#comment-952940
I think it'd be a great idea to include xen in [extra], and I'm
won
Hello!
I've been maintaining xen and associated packages for a few years.
This relative evening the package got the following comment:
https://aur.archlinux.org/pkgbase/xen#comment-952940
I think it'd be a great idea to include xen in [extra], and I'm
wondering if there's some way I could
Changing the license does indeed change the package, as it means that
different license files are installed, though I'm not sure whether that
warrants bumping the pkgrel, and spamming the same comment across
several packages by the same maintainer is certainly disruptive. That
said, I've only s
I've been going through my 400+ AUR packages updating the license to match SPDX
license requirements.
xiota has decided a pkgrel bump is required if one updates the license. He has
begun spamming the same comment on 9 of my AUR packages so far. I've already
told him to stop here:
https://aur.a
