Hello,
First-time AUR packager here. I am working on a PKGBUILD for a program that optionally supports wayland, and optionally supports xorg.
When you configure the program, you specify one, the other, or both, of --enable-wayland and --enable-xorg. Specifying either option implies a build-time and a run-time dependency on the relevant client libraries.
I could build a single package with dependencies on both, but I suspect most wayland users would want the wayland-only package, and vice-versa for xorg.
Is this a use-case for split-package? Trying not to overcomplicate things.
Thanks.
-hossbeast
On 17/10/2021 05:52, todd freed via aur-general wrote:
Is this a use-case for split-package?
Very likely. I'd probably package them as $pkgname-wayland and $pkgname-xorg and have them both provide $pkgname.
(Though, if one backend was the upstream default then I might package that as $pkgname and the alternative as e.g. $pkgname-xorg)
J
Sounds good.
Though, if I build a couple variants from a single PKGBUILD (which I think is what split-package means), wouldn't users need to have dependencies installed sufficient to build all of them? In that case, should I have separate PKGBUILD files?
Thanks again.
-hossbeast
On Sun, Oct 17, 2021 at 4:00 AM Jonathon Fernyhough via aur-general aur-general@lists.archlinux.org wrote:
On 17/10/2021 05:52, todd freed via aur-general wrote:
Is this a use-case for split-package?
Very likely. I'd probably package them as $pkgname-wayland and $pkgname-xorg and have them both provide $pkgname.
(Though, if one backend was the upstream default then I might package that as $pkgname and the alternative as e.g. $pkgname-xorg)
J
On 17/10/2021 15:42, todd freed wrote:> Though, if I build a couple variants from a single PKGBUILD (which I
think is what split-package means), wouldn't users need to have dependencies installed sufficient to build all of them?
Whatever is listed in the top-level depends and makedepends will be installed during package build. Package-specific depends can be listed (or appended to) within the each split package's _package() function (otherwise the top-level depends is used).
In that case, should I have separate PKGBUILD files?
No, a split package is appropriate. PKGBUILD files are intended for package maintainers, not for consumption by AUR helpers. ;)
Hi,
I hope you had a good weekend!
On Sat, 2021-10-16 at 21:52 -0700, todd freed via aur-general wrote:
Is this a use-case for split-package? Trying not to overcomplicate things.
If you do decide to go the split package route, make sure you consider that some users switch between Xorg and Wayland and might want both options.
Thanks, Maxwell
Hi, I posted the PKGBUILDS onto the AUR forum. Any feedback appreciated.
https://bbs.archlinux.org/viewtopic.php?pid=2000975
-hossbeast
On Sun, Oct 17, 2021 at 4:45 PM Maxwell G gotmax@e.email wrote:
Hi,
I hope you had a good weekend!
On Sat, 2021-10-16 at 21:52 -0700, todd freed via aur-general wrote:
Is this a use-case for split-package? Trying not to overcomplicate things.
If you do decide to go the split package route, make sure you consider that some users switch between Xorg and Wayland and might want both options.
Thanks, Maxwell
-- Maxwell G (@gotmax23) Pronouns: He/Him/His PGP Key Fingerprint: f57c76e5a238fe0a628e2ecef79e4e25e8c661f8 gotmax@e.email
aur-general@lists.archlinux.org