Package User system [was:Re: [Bug 1536] ]

Randy McMurchy LFS-User at
Sun Aug 21 23:29:30 PDT 2005

Bruce Dubbs wrote these words on 08/22/05 01:13 CST:

> Well, I have lately been following a suggestion that DJ made some time
> ago.  For the make install, I do make DESTDIR=/tmp/packagename-inst
> install and then I can see all the files installed by that package.

To me, this is the same as installing in /home/buildusername/packagename


> Of course, this method doesn't work in all cases but when it does work,
> it gives a nice tree of files installed.  It's easy to get an installed
> size too.  When it doesn't work, each package has to have a specialized
> workaround created.

I *always* do this with new packages, or unknown packages. Biggest thing
is the propensity to install in /usr/etc/packagename for dickhead
packages that don't use /etc by default. Installing once in a private
dir gives you so much heads-up as to what to expect.

> Since you do a `find /` twice for each build, how long does that take?

Actually, it takes a second at the most. I do this find and then a du
at the beginning and end of each build. I have lots of RAM, and the
find and du data appears to be cached, so time is minimal for me.

But then, I spend much time building packages for BLFS so the machine
is bound to have cached data for 'find' and 'du' stuff.

> I note that your script depends on how filesystems are set up.  For
> instance, I  don't think it would work as is if /usr was on a separate
> partition.

Indeed, filesystems would be an issue. However, I build on top of
one partition that houses everything. Granted, I have many partitions,
hence the -xdev in the finds, but /usr /home /tmp /srv /you-name-it
are all on one partition.

Of course, if I were to have multiple filesystems set up, I would
have to modify the find command.


rmlscsi: [GNU ld version 20041220] [gcc (GCC) 3.4.3]
[GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686]
01:20:00 up 142 days, 53 min, 3 users, load average: 0.33, 0.78, 0.71

More information about the blfs-book mailing list