<div class="gmail_quote">On Fri, May 29, 2009 at 02:36, Eric Hameleers <span dir="ltr"><<a href="mailto:alien@slackbuilds.org">alien@slackbuilds.org</a>></span> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div class="h5">
</div></div>Hi Grissiom<br>
<br>
If you write a SlackBuild that installs purepython files which are<br>
architecture independent you will indeed still have a "lib vs lib64"<br>
difference in the final package depending on the architecture you<br>
create the package on.<br>
But since we are SlackBuilds.org and not LinuxPackages.net we do not<br>
have to worry about where the final package gets built and installed -<br>
the person who compiles it will know.<br>
</blockquote><div><br>Hmm, Ok, so I know the role of SlackBuilds.org -- distribute the build script but not the packages and there is no guarantee that the packages build from the scripts are re-distributable?<br> </div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
So, the purepython package can be "noarch" as long as you determine<br>
the install-lib using Python itself:<br>
<br>
PYTHONLIB=$( python -c "from distutils.sysconfig import<br>
get_python_lib; print get_python_lib()" )<br>
<br>
This will yield "/usr/lib/python2.5/site-packages" on Slackware 12.2<br>
and "/usr/lib64/python2.6/site-packages" on slackware64-current. You<br>
see that the python version number no longer needs to be hardcoded.<br>
<br>
Use that variable as follows:<br>
<div class="im"><br>
python setup.py install \<br>
--prefix=/usr \<br>
</div> --install-lib=$PYTHONLIB \<br>
--root=$PKG<br>
</blockquote><div><br>The setup.py will take care of this automaticially. Maybe there is no need to bother --install-lib if you do not want to re-distribute the package. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You will not have to add the "if ARCH ... fi" block and the<br>
LIBDIRSUFFIX is not used at all. A single SlackBuild will work on all<br>
Slackware releases.</blockquote><div><br>Yes, SlackBuilds will always work. So the problem now is the package build from a SlackBuild is re-distributable or not or, do we want it to be re-distributable?<br> </div></div>-- <br>
Cheers,<br>Grissiom<br>