-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 15 Aug 2004 02:32:22 GMT, Joost Kremerwrote:
> Bradley Reed wrote:
>>> make install DESTDIR=/tmp/build
>>
>> Often good to run make -n install DESTDIR=/tmp/build first to see if
>> the Makefile honors DESTDIR.
>
> and when doing it for real, keep a log file:
>
> make install DESTDIR=/tmp/build > install.log 2>&1
>
> sometimes DESTDIR is honoured for most of the install commands, but not for
> all.

I've definitely seen this. It's annoying.

> sometimes there are commands that are only executed when DESTDIR is
> not set.

Wasn't aware of this, good to know.

> with keeping an install.log you can track these things and correct
> them.
>

Good advice. I'll add it to my package making notes.

Thanks,
Brad



-----BEGIN PGP SIGNATURE-----

iD8DBQFBHs7KkDp4KjYna1ARAlHUAJ4pcl4o65Ty6N8WgCHv+B bhM4fOlQCgnxGf
jZYb9ich/31h4LTwYsyDM+o=
=ryJY
-----END PGP SIGNATURE-----

Bradley Reed wrote:
>> sometimes there are commands that are only executed when DESTDIR is
>> not set.
>
> Wasn't aware of this, good to know.

i've seen it happen with libtool. it gives a message saying you should run
'libtool --finish' on dir so-and-so. i usually put a command to that effect
in the install script. seems to work fine.

--
Joost Kremers joostkremers@yahoo.com
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)

On 08-14-2004, in alt.os.linux.slackware,
Bradley Reed <bradreed@NOSPAMcomcast.net> wrote:

> On 10 Aug 2004 23:03:06 -0500, +Alan wrote:
>>
>> In alt.os.linux.slackware, Zebee Johnstone dared to utter,
>>> The doco's a bit light on... I understand that all I get is a
>>> tarball and an install file, but there are presumably right ways
>>> and wrong ways of doing the install file?
>>
>> ./configure
>
> Often good to specify --prefix= and --sysconfdir= on the
> ./configure
>> make
>> make install DESTDIR=/tmp/build
>
> Often good to run make -n install DESTDIR=/tmp/build first to see
> if the Makefile honors DESTDIR.

Also useful to look for $(DESTDIR) in the Makefile (generated after
../configure) and/or the Makefile.in prior to configure. Besides
determining if DESTDIR is supported at all, you can get a pretty
good idea of whether or not DESTDIR is *fully* supported. Sometimes
it's only partially implemented.

Max

--
For every evil under the sun,
There is a remedy, or there is none;
If there be one, try and find it,
If there be none, never mind it.

On 08-13-2004, in alt.os.linux.slackware,
Joost Kremers <joostkremers@yahoo.com> wrote:

> Max wrote:
>> NOTE: I'm not one that thinks non-distro related third party
>> bullshit *needs* to be shoved into /usr/ by default. The
>> linuxpackages "standard" says otherwise.
> [...]
>> Is it a "slackware standard" or a "linuxpackages standard"? Or,
>> more importantly, is all of this just a "'Max' standard" way of
>> thinking?
>
> IMO /usr/local should be reserved for stuff that i compile and
> install myself. so everybody that's not me should keep their
> smelly paws off of it. ;-)

Luckily for me, coming from a single user/single machine, the only
smelly paws I have to worry about are my own. But then, maybe that
isn't so lucky since I can't seem to keep my smelly paws off of
nothing.

> btw, when i compile something and create a tgz from it, i always
> put it in /usr as well. just because it *is* a packages.
> /usr/local is for stuff that is not packaged up nicely.

Well, I'll have you know that my packages targeting usr/local look
pretty nice if I do say so myself.

Max

--
For every evil under the sun,
There is a remedy, or there is none;
If there be one, try and find it,
If there be none, never mind it.