Re: easy way to tell if "in" package build?
Jules Bean <jmlb2@hermes.cam.ac.uk> writes:
> Marcus Brinkmann wrote:
> >
> > On Mon, Oct 18, 1999 at 11:59:49AM -0500, othman@cs.wustl.edu wrote:
> > > I just patched Debian's libtool to no longer encode library paths into
> > > binaries if the binary is built on Debian systems, but I think the
> > > patch is too limiting and it is only meant to be a temporary hack. What
> > > I'd like to do is disable library path encoding *only* if a Debian
> > > package is being built, i.e. if libtool is executed in the middle of a
> > > build started by debuild.
> > >
> > > Can someone suggest a way to tell if we are in the middle of a Debian
> > > package build?
> >
> > There is no way to do so, and any derivation from the upstream behaviour in
> > libtool is evil. Please do not use such a patch in the Debian package (it
> > would only make me to use the upstream libtool).
>
> Marcus: You mean deviation, right?
>
> Ossama: The right technical answer surely is to have some kind of
> /etc/libtool.conf, which we set up on debian systems to indicated no
> hard-coded paths?
>
> More generally, I could believe that there might be circumstances when
> we need to know if we're in a package build, and the right answer to
> that sort of problem is almost certainly an environment variable, to be
> set up by dpkg-buildpackage, say.
Wouldn´t it be far better to tell libtool via /etc/libtool.conf what
paths it should use relative and not absolut?
Anything that goes to /lib or /usr/lib or /usr/share/lib and so on is
debians domain and should be relative paths. Libs in /usr/local/lib or
/opt/lib on the other side should be absolut.
That way package would build right and your own programs also, or not?
May the Source be with you.
Goswin
Reply to: