On Tue, Aug 23, 2016 at 11:41 PM, Eli Schwartz via aur-general < aur-general@archlinux.org> wrote:
All Python build commands can be put into package(), while GTK applications not. It doesn't make a difference with current pacman and makepkg,
On 08/23/2016 11:27 AM, Chi Hsuan Yen via aur-general wrote: though.
You can put whatever commands you want in package(), gtk or otherwise. Which I think is exactly what you are doing in regards to python.
The package() function is meant to separate the final step of copying over files into the pkg/ tree independent of everything else, ideally src/ should be treated as close to readonly as possible during package().
During the installation of a python package, it figures out the list of modules defined in setup.py and copies them into the right hierarchy in build/ as well as compiling any potential binary components. Then it copies the contents of the build/ hierarchy (whatever that may be, irrespective of the original source code) into the installation root.
Just because it is copying files around rather than running them through a C compiler, that makes it less of a build() sort of thing???
-- Eli Schwartz
Shamefully I didn't study the package guidelines carefully. I write PKGBUILDs for Python packages by copying from the (somewhat out-dated) Python PKGBUILD template [1], which is encouraging the wrong way. Official packages, like python-pip or python-virtualenv, use a similar approach too. [1] https://git.archlinux.org/abs.git/tree/prototypes/PKGBUILD-python.proto