<br><br><div class="gmail_quote">On Thu, May 28, 2009 at 10:40 PM, <span dir="ltr"><<a href="mailto:xgizzmo@slackbuilds.org">xgizzmo@slackbuilds.org</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="im">On Thursday 28 May 2009 21:15:55 Grissiom wrote:<br>
> ><br>
> > IMHO, if a package uses */lib64 then it's an ARCH=x86_64 package.<br>
> ><br>
><br>
<br>
</div>This seems to be what Slackware does. I think the best thing to do<br>
here is just to make sure we use ARCH=${ARCH:-noarch} and not hard<br>
code it. That way if the package builder is building for x86_64<br>
then they should be using ARCH=x86_64 ./some.SlackBuild and it will<br>
have an x86_64 tag on the final package. So far all of the python<br>
builds I have seen that use setup.py find the right python path<br>
on their own, so the SlackBuild does not have to be changed in<br>
any other way.<br>
</blockquote><div><br>I don't like the idea of defaulting to noarch if the package is incompatible with x86_64. If we're going to have separate packages, they should be clearly marked as such. Making one 'noarch' and one 'x86_64' is inconsistent. It's either 'noarch' or it isn't. <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;"><br>
--dsomero<br>
<div><div></div><div class="h5"><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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><a href="http://www.dragonwisard.net/">http://www.dragonwisard.net/</a><br>