[aur-general] AUR Best Practice for New Package Upload
stef_204 at yahoo.com
Tue Sep 16 12:56:58 UTC 2014
On Tue, 9/16/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: Tuesday, September 16, 2014, 1:42 PM
There is no obligation to have
Usually, when it is provided by
upstream, it is used to ease the
This is not the best approach. Usually /opt is
used for *large*
Since it's an
application and not a library, one should only install
python3 version of the scripts, since
this is the default version of
I would install masshash and
masshash-launcher directly in in /usr/bin.
No need for the symlinks.
I wouldn't install the README.md and the
Usually, those files belong to
the source archive and are not deployed.
However, you can as well put them in
/usr/share/doc/masshash if you
I would also add a .desktop
file to allow the mashhash-launcher to be
run from your desktop environment without
having to open a terminal for
And finally, I would create a split package for
this application. One
for the console
application only and one for the GUI.
No /opt for your package ;)
For the exercice, I packaged the application,
and you can find the
result here  (in the
Feel free to inspire
yourself, or simply to take it as it is if you
Try to study it and feel
free to ask any questions you want about it.
Nuno Araujo <nuno.araujo at russo79.com>
Thanks a lot for helpful feedback.
I was kind of hoping no one would write a PKGBUILD for this so I would not be tempted to use a shortcut and "cheat" but hey.... ;)
I will use your PKGBUILD and files as a model, really make sure I understand them fully, make any modifications as desired and post here final result (if different from yours.)
I may have some questions and will post here if any.
More information about the aur-general