Arch Linux

8539 readers

2 users here now

The beloved lightweight distro

founded 6 years ago

MODERATORS

k_o_t@lemmy.ml

Forks of packages on AUR (programming.dev)

submitted 1 year ago by 0WN463@programming.dev to c/archlinux@lemmy.ml

2 comments fedilink hide all child comments

Hey, how do we generally handle forks of packages that we wish to use on the AUR?

For example, we have package A on the AUR and we have A-fork with a feature that is not merged into A due to various reasons (dead projects, other concerns, etc).

Do we create a new AUR package that is based off that fork? Wouldn't that pollute the AUR with packages that are similar but are forks of each other?

What if I am developing a package B that depends on the A-fork that is not in the AUR? Do I have to create A-fork as an AUR package so that my package B can be built?

you are viewing a single comment's thread
view the rest of the comments

[–] exu@feditown.com 3 points 1 year ago

I don't think there's concrete guidance.

If the original package is dead, you might be able to convince the AUR maintainer to switch to the fork.

In other cases, maybe a package with added in the name could be created. I'd posit Supersonic as an example, where alternative packages exist just for enabling Wayland. It's still the same upstream, but an additional option in the build is required to enable Wayland.

Similarly, Emacs offers multiple versions with different build flags, though in this case it is using the same PKGBUILD for all versions.