[Slackbuilds-users] [FYI]SlackBuild for python modules should be architecture dependent
chaos.proton at gmail.com
Fri May 29 11:14:34 UTC 2009
On Fri, May 29, 2009 at 12:08, Chess Griffin <chess at chessgriffin.com> wrote:
> I am probably missing the finer points of this discussion, but it seems
> to me that the current system works just fine. User A on a 32 bit
> system who has not set ARCH as an environmental variable and builds a
> package from a 'noarch' SlackBuild script, will end up with a package
> with 'noarch' in the name and libraries in /usr/lib. That can be
> re-distributed between other 32 bit systems. OTOH, User B on a 64 bit
> sysem who has set ARCH as 'x86_64', either in the environment or
> passing it to the SlackBuild script, will end up with a package with
> 'x86_64' in the name, with libraries in /usr/lib64 which can be
> redistributed between other 64 bit systems.
Yes, but currently some packages build from SlackBuilds(mostly for python
modules) will install thing into /usr/lib64 even have "noarch" tag.
> The truly independent 'noarch' packages are those simple ones that
> simply build a single /usr/bin/ binary with make or that install icon
> sets or something.
Hmm, I think rworkman will agree with you.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SlackBuilds-users