[aur-general] Are AUR VCS packages that depend on AUR VCS packages from other projects a good idea and who should decide on that ?

Lone_Wolf lonewolf at xs4all.nl
Tue Apr 30 23:07:43 UTC 2019

Thanks for speaking freely, scimmia.

The env var idea has been thrown out of the window.

Time to summarize and tally .

Option A. mesa-git depends on llvm trunk and PKGBUILD editing is needed 
for those that want to build against stable llvm.

Option B. mesa-git depends on llvm stable and those that want to build 
against llvm trunk need to edit the PKGBUILD.

In 2012 there were many mesa trunk packages in AUR. Over time the next 
years most disappeared or were merged.

from approx 2014 on 2 popular mesa trunk packages remained : mesa-git by 
krezji and mesa-radeon-git by me.

A big difference was that mesa-git used option B while mesa-radeon-git 
used option A.

In august 2015 [1] krezji announced he didn't have time to maintain his 
packages anymore.

I took over mesa-git, switched mesa-git to option A and submitted a 
deletion request for my mesa-radeon-git package.

Option A is favored by many post 2015 mesa-git users and myself and 
acceptable to ESchwartz.

Option B is favored by scimmia, bruno, a mesa developer and atleast 2 
mesa-git users that discussed this issue with him.

I don't see a way to combine option A & B in one package but feel i 
can't ignore the requests for option B.

At this point in time the likely outcome seems that I adjust mesa-git to 
use option B.

I'll create new packages for option A under a new pkgbase, maybe 

Then I'll post a call for a new mesa-git maintainer. I'll keep 
maintaining both mesa trunk sets of packages for about a month, if no 
new maintainer for mesa-git is found by then it will become an orphan.

I don't like abandoning a package but I can't maintain something I 
disagree with.

I'll give myself a few days to think this over before deciding.



More information about the aur-general mailing list