[aur-general] AUR Best Practice for New Package Upload
stef_204 at yahoo.com
Wed Sep 10 15:58:21 UTC 2014
On Wed, 9/10/14, Nuno Araujo <nuno.araujo at russo79.com> wrote:
Subject: Re: [aur-general] AUR Best Practice for New Package Upload
To: aur-general at archlinux.org
Date: Wednesday, September 10, 2014, 1:23 PM
Well, you can make a
split package. This way you only have a PKGBUILD to
maintain. AUR now supports them by default so I
see no major issues
The rule of thumb that I tend
to apply now is:
Write a single PKGBUILD per
Make it a split package if
Nuno Araujo <nuno.araujo at russo79.com>
Nuno, sorry but I'm lost here. To me a "split package" is 2 separate packages, one for the CLI and another one for the GUI. The GUI will only include the GUI itself (GTK+) obviously and not the actual program which will be listed as a dependency.
So, does that not imply 2 separate PKGBUILD's and 2 separate packages? One for CLI and one for GUI?
Sorry but I'm obviously missing something. I looked at wiki AUR packaging standard but not finding what you are referring to. You are referring to a single PKGBUILD.
Can you please explain or refer me to proper wiki section?
More information about the aur-general