[aur-general] AUR Best Practice for New Package Upload

[Johannes Löthberg]

On 06 Sep 2014, at 12:06, stef <stef_204 at yahoo.com> wrote:
> 1) the main script which is CLI (available for python2 and/or python3)
> 2) a GTK+ GUI (optional) for python2
> 3)  the GTK+ GUI (optional) for python3
>
> I use the GTK+GUI for python3 on my box but perhaps some users might want (or have to)
> use python2.
>
> Question 1):
>
> The program is small (approx 250kb only) and my tendency would be to just do the one
> package with all 3 components which users will then use as they see fit, CLI only or
> GUI, etc.  This would allow me to maintain only one package for this program.
>
>Is only one package OK with the AUR community?

You shouldn’t mix python2 and 3. Make it a split package.

> Question 2) I just basically downloaded the source tarball, extracted it to /opt and
> am running it from there.
>
> My idea is to achieve the same with PKGBUILD, following proper protocol, etc.
>
> Is “installing” (extracting dir structure) to /opt a problem?

Don’t do that, it’s very ewwy. Read up on how and where python packages are normally packaged.
Or actually, read up on setuptools and write a setup.py that you can use in the PKGBUILD.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1536 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mailman.archlinux.org/pipermail/aur-general/attachments/20140906/d78631b3/attachment-0001.asc>