I think what Eric was saying is that the Slackbuild is architecture independent but the package generated by it is architecture dependent. That seems to be enough to satisfy him. <br><br>Personally, I see no reason why the package should *need* to be architecture dependent. We're restricting it based on a directory structure convention. It would be relatively easy to just use symlinks to have the modules show up in both places if appropriate. I see no reason to have two separate packages when the contents are identical and the only difference is where they get installed. It's a waste of space and adds unnecessary complexity to administration. <br>
<br><div class="gmail_quote">On Thu, May 28, 2009 at 7:10 PM, Grissiom <span dir="ltr"><<a href="mailto:chaos.proton@gmail.com">chaos.proton@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div class="im">On Fri, May 29, 2009 at 02:36, Eric Hameleers <span dir="ltr"><<a href="mailto:alien@slackbuilds.org" target="_blank">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>
</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><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>
<div class="im">
<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><br>
python setup.py install \<br>
--prefix=/usr \<br>
</div> --install-lib=$PYTHONLIB \<br>
--root=$PKG<br>
</blockquote></div><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><div class="im"><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><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><font color="#888888">Grissiom<br>
</font><br>_______________________________________________<br>
SlackBuilds-users mailing list<br>
<a href="mailto:SlackBuilds-users@slackbuilds.org">SlackBuilds-users@slackbuilds.org</a><br>
<a href="http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users" target="_blank">http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users</a><br>
Archives - <a href="http://lists.slackbuilds.org/pipermail/slackbuilds-users/" target="_blank">http://lists.slackbuilds.org/pipermail/slackbuilds-users/</a><br>
FAQ - <a href="http://slackbuilds.org/faq/" target="_blank">http://slackbuilds.org/faq/</a><br>
<br>
<br></blockquote></div><br><br clear="all"><br>-- <br><a href="http://www.dragonwisard.net/">http://www.dragonwisard.net/</a><br>