Bruce Dubbs wrote these words on 12/07/05 15:56 CST: > Randy, is there anything else you do regularly?
1) Well, as you mentioned I use BC for the SBU and disk space calculations. In fact, I must build BC in Chapter 5 LFS and in the chroot phase of LFS as well. 2) I also log all files that are put to disk. That way it makes it easy to determine if the installed programs, libraries and directories are accurate. This also serves for package management for me. For instance, if I update a version of a package to an exiting installation, I remove all the files first, then install the new version. This way, I again have a log of all installed files. This also serves the purpose of cleaning up any files that may now be obsolete and aren't required to be on disk any longer. 3) I try to examine the source directory to see if documentation is installed. I've found you simply can't rely on the package installation to install docs. Sometimes there is a 'make docs' or 'make docs install' (or some equivalent) target that must be run. Other times, it is just adding manual installation of existing documentation in the source tree to /usr/share/doc/package-1.2.3. If there are no pre-made docs, and there is a particularly good sgml or texi file that provides good information, I'll use hand commands to generate and then install docs. 4) I try to remember to click on both download links and ensure that they lead to accurate URLs. I don't actually download, just ensure that it isn't a dead link. 5) Recently, I've tried to remember to make sure that whatever commands should be issued by root are prefaced with 'role=root' in the <screen> tag. This is especially important now that Manuel is almost done tagging all the files for this new automated system. 6) Dependencies are probably the most difficult thing to accurately determine. Sometimes it is easy by carefully perusing the log from the 'configure' script. README, INSTALL and docs located on the maintainer's web site should be checked. Recently, the changes to Pkg-Config (things can be made to be much less verbose now) makes things hard. Used to be that for instance some GNOME package would check for Dependency1 like this: Checking for dependency1.... dependency 1a found dependency 1b found dependency 1c found .... dependency1 libs = (list of libs) etc. Now, you get this: Checking for dependency1.... found And that is it. You have to manually examine the configure script to really see what all dependency1 is. Anyone who's ever tried to look through your average configure script knows that this is really a drag. Anyway, there may be more I do during package updates, but I can't recall right now. Hope this helps. -- Randy rmlscsi: [GNU ld version 2.15.94.0.2 20041220] [gcc (GCC) 3.4.3] [GNU C Library stable release version 2.3.4] [Linux 2.6.10 i686] 01:42:01 up 74 days, 11:06, 3 users, load average: 0.15, 0.12, 0.19 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
