Hello all!
I (try to) maintain the Xen stuff in AUR.
As background:
There are multiple ways to boot a VM inside of Xen. For full hardware
emulation, I can use SeaBIOS or edk2-ovmf as appropriate. For
paravirtualization there is the newer PVH method, and the older PV
method. Both are supp
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-
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
On 2/6/22 05:51, Uwe Koloska via aur-general wrote:
But wasn't the request about splitting off the library part from a
bigger package that contains all about xen? So that there is a xen-lib
split-package and the rest, so that everyone providing services for
xen, could be build with only the
On 2/6/22 04:46, Morten Linderud via aur-general wrote:
Arch doesn't split off libraries and development headers into seperate packages
and this is a feature. There are few exceptions to this but generally I
don't think there is anything written about this.
I understand this is not something
Hello!
I maintain the xen package in AUR, and I recently got a merge request on
my private repo to split the libs off into a split package in order to
make building packages for things like ocaml a little easier.
Previously, packages depended on a now outdated xenstore package.
I have a va
On 6/22/21 3:16 AM, alad via aur-general wrote:
There's 59 TUs looking after 70676 packages and moderating 85141
users. To make that manageable, you need some a strict set of rules.
One of them is not submitting "-latest" packages that are already in
the repos.
But the implementation is not
On 6/22/21 1:48 AM, Caleb Maclennan via aur-general wrote:
As background, many years ago when working as an audio engineer I used to
use it in production nearly full time. I'm quite familiar with it's past
and the weird development practices upstream (such as forked toolkit
versions). I am no l