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

Grissiom chaos.proton at gmail.com
Thu May 28 14:25:37 UTC 2009

On Thu, May 28, 2009 at 22:09, Dragon Wisard <dragonwisard at gmail.com> wrote:

> Since they bytecode is itself, platform independent, wouldn't it make sense
> to just use one directory (eg. /usr/lib/python2.6/site-packages/xxx) and
> symlink the /usr/lib64/... to the that directory? Assuming you have both
> 32-bit and 64-bit builds of Python installed, there is no sense in having to
> install the same exact modules twice in two different locations.
> I would opt to install everything in /usr/lib/... since that will always be
> present, and then create a symlink from doit.sh if x86_64 is detected.
> Just my 2 cents.

Yes, install them twice make no sense at all because in slackware32, python
is installed in /usr/lib while in slackware64, python is installed in
/usr/lib64. At least there is no official 32-bit python in 64-bit
environment now.(maybe never?) Symlink is something like install "twice"
except comsume less disk space.

In my slackware64, the sys.path(where python looks for modules) is:

['', '/usr/lib64/python26.zip', '/usr/lib64/python2.6',
'/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk',
'/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload',

so, 64-bit python does not look for things in /usr/lib/pythonx.x/xx I think
32-bit python does not look for things in /usr/lib64 too. This is why the
packages are "arch dependent"

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

More information about the SlackBuilds-users mailing list