[Slackbuilds-users] [FYI]SlackBuild for python modules should be architecture dependent

Dragon Wisard dragonwisard at gmail.com
Fri May 29 02:59:18 UTC 2009

On Thu, May 28, 2009 at 10:40 PM, <xgizzmo at slackbuilds.org> wrote:

> On Thursday 28 May 2009 21:15:55 Grissiom wrote:
> > >
> > > IMHO, if a package uses */lib64 then it's an ARCH=x86_64 package.
> > >
> >
> This seems to be what Slackware does. I think the best thing to do
> here is just to make sure we use ARCH=${ARCH:-noarch} and not hard
> code it. That way if the package builder is building for x86_64
> then they should be using ARCH=x86_64 ./some.SlackBuild and it will
> have an x86_64 tag on the final package. So far all of the python
> builds I have seen that use setup.py find the right python path
> on their own, so the SlackBuild does not have to be changed in
> any other way.

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.

> --dsomero
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20090528/adb742cc/attachment-0001.htm>

More information about the SlackBuilds-users mailing list