On Tue, Dec 25, 2012 at 02:02:43PM +1300, Simon Geard wrote: > On Mon, 2012-12-24 at 10:34 -0800, Paul Rogers wrote: > > For myself, after my first LFS-4.1 build, all by hand with copious > > written notes from the book, I began using a "directory watcher" called > > "git" by Ingo Bruekel. It was apparently "abandon-ware", and I found a > > few "fixes" necessary. And of course, the name got usurped. So I > > renamed my version, but I still use it. My build scripts basically > > encapsulate the commands in the book. > > That's not a bad idea, actually - using filesystem monitoring to track > file and directory creation during "make install". Nicer than the old > LD_PRELOAD hacks I used to use, and probably faster than the DESTDIR > approach I use now... > Whatever works for you. For myself I'm using:
(i.) variants of find -H / (or /tools) - excluding directories I don't wish to know about (e.g. my logs) both before I start to build the package, and after, then feed both lists to diff -n | grep '^/' to find what was _installed_ plus (ii.) then running a similar diff on the 'installed' and 'after' files to find any files which were modified/updated. But then, I'm an admitted heretic - in my scripts I build and install as root : DESTDIR/INSTALL_ROOT are for when I'm looking at a package, not when I'm installing it ;) To be honest, I spent some weeks trying to use DESTDIR installs as a user while I was reworking my scripts, but I didn't find it worth the aggravations. Happy Xmas. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
