On Fri, Aug 31, 2018 at 11:52:42PM +0200, Thomas Trepl via blfs-support wrote:
>
> More generally spoken, the DESTDIR-method is pretty fine as long as you
> take in account that sometimes the sequence of the instructions needs
> to be changed. I assume you do DESTDIR to provide binary packages for
> other machines than the building machine - which is IMHO the only
> reason DESTDIR makes sense.
Not at all: it lets you see exactly what is going to be installed.
e.g. When building a new package, or new version:
Does a package really need --disable-static, or are no static libs
installed ?
How much space does the install take ?
Of course, not all packages support DESTDIR, some Python modules and
Qt packages need a different magic word. Also one or two others,
and sometmes you still need to be root to run it.
Some editors document these things in the xml, which is only handy
when you come to make the edit : by that point I (hope to) know what
I'm going to put in the book. When I remember, I usually put these
things in the wiki. For Python modules using setup.py, --root
/some/dir usually works.
ĸen
--
Also Spuke Zerothruster
(Finnegans Wake)
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
