On Sunday 02 January 2005 23:44, Levi Bard wrote:
> > The issue as to upstream code is if it hardcodes constructs as
> > '/usr/lib/' rather than letting ./configure, and the
> > autotools, and the compiler and linker substitute in a more
> > likely /usr/lib64/ type path. As to packaging, the issue is
> > similar, as a novice packager may likewise use hardcoded
> > library paths rather than the %_lib construct. As to SuSE
> > support maturity, I do not follow this distribution as its
> > development process is essentially closed for large portions.
>
> That's part of the reason why the /usr/lib64 type path is horribly,
> horribly wrong for an amd64 distribution.
Hmmmmmm.....Thanks ????? guys !!!. My head is beginning to hurt !!!
Doesn't answer the question but I guess there is no definitive answer.
Soooo... I guess I could just rebuild the .src, not worry about any
SPECS, and see what happens ???
Bob S.
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:03:04 EDT