cvs commit: hints install-log.txt

timothy at linuxfromscratch.org timothy at linuxfromscratch.org
Thu Oct 24 06:11:56 PDT 2002


timothy     02/10/24 06:11:56

  Modified:    .        install-log.txt
  Log:
  Updates by author.
  
  Revision  Changes    Path
  1.3       +47 -24    hints/install-log.txt
  
  Index: install-log.txt
  ===================================================================
  RCS file: /home/cvsroot/hints/install-log.txt,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- install-log.txt	26 Aug 2002 20:54:16 -0000	1.2
  +++ install-log.txt	24 Oct 2002 13:11:55 -0000	1.3
  @@ -1,13 +1,22 @@
   TITLE		install-log
  -LFS VERSION:	3.2
  +LFS VERSION:	4.0 and newer
   AUTHOR:		Andy Goth <unununium at openverse.com>
   
   SYNOPSIS:
   	How to manage packages with install-log
   
   HINT:
  -Version 1.0: 2001-12-17: First release
  -Version 1.1: 2002-08-13: Corrections and updates for recent lfs books
  +Version 1.0: 2001-12-17: First release.
  +Version 1.1: 2002-08-13: Corrections and updates for recent lfs books.
  +Version 1.2: 2002-10-20: Updates regarding new developments in install-log.
  +
  +The latest version of this file should be at:
  +
  +http://ioioio.net/devel/install-log/install-log/LFS-HINT
  +
  +And it should be mirrored at:
  +
  +http://hints.linuxfromscratch.org/hints/install-log.txt
   
   This hint covers install-log, a simple package management tool.  It discusses
   how to set up install-log, how to use it to make installation logs, and how to
  @@ -15,8 +24,8 @@
   install-log during all stages of lfs installation.
   
   This version of the hint discusses install-log 1.9, and the general ideas
  -should apply to any version of lfs.  In fact, much of it isn't even
  -lfs-specific but still useful for any UNIX system that doesn't already have
  +should apply to any version of lfs.  In fact, much of it isn't even lfs-
  +specific but useful for any UNIX system that doesn't already have suitable
   package management.
   
   +-----------------------------+
  @@ -27,10 +36,17 @@
   
   http://prdownloads.sourceforge.net/install-log/install-log-1.9.tar.bz2
   http://install-log.sourceforge.net/release/install-log-1.9.tar.bz2
  +http://ioioio.net/devel/install-log/install-log-1.9.tar.bz2
   http://www.pengaru.com/~andy/packages/install-log-1.9.tar.bz2
   
   The tarball is 10k in size, just like this hint. ;^)
   
  +Or, you can get the very latest code using one of the following:
  +
  +http://ioioio.net/devel/install-log/install-log-cvs.tar.bz2
  +$ cvs -d:pserver:anonymous at ioioio.net:/var/lib/cvs/install-log co install-log
  +http://users.openverse.com/cgi-bin/viewcvs/install-log/install-log/
  +
   Then unpack, compile, and install:
   
   make &&
  @@ -40,11 +56,11 @@
   mkdir /var/install-logs &&
   touch /var/install-logs/.timestamp
   
  -And we're golden.  Note that the makefile has no "install" target.
  -Also it produces a couple scary-looking error messages the first
  -time you compile.  Ignore them.
  +And we're golden.  Note that the 1.9 makefile has no "install" target.  Also it
  +produces a couple scary-looking error messages the first time you compile.
  +Ignore them.
   
  -Alternately, you can test install-log out right away. Use this variant:
  +You can test install-log out right away by using this variant of the above:
   
   make &&
   cp install-log /usr/bin &&
  @@ -52,13 +68,13 @@
   cp install-log.rc /etc &&
   mkdir /var/install-logs &&
   touch -r . /var/install-logs/.timestamp && 
  -install-log install-log &&
  -cat /var/install-logs/install-log
  +install-log install-log -E cat -e
   
  -Instead of merely creating the .timestamp file, this sets its, uhm, timestamp
  -to equal that of the install-log-1.9 source tree.  It then runs the install-log
  -program to take note of its own installation.  Wow.  And finally, it cats the
  -log to verify its contents, which should be:
  +Instead of merely creating the .timestamp file, this sets its, err, timestamp
  +to equal that of the install-log-1.9 source tree, which should be older than
  +the just-installed install-log program but newer than everything else on the
  +system.  It then runs install-log to take note of its own installation.  Wow.
  +It also cats the log to verify its contents, which should be:
   
   /usr/bin/install-log
   /usr/share/man/man1/install-log.1
  @@ -66,13 +82,20 @@
   This is as you'd expect, except that install-log.rc doesn't show up.  This is
   because, by default, install-log doesn't scan the /etc directory.
   
  +I fixed the silly makefile problem (no install target) in versions beyond the
  +(ancient) 1.9, so you can skip all the above and instead type make install.  It
  +should even do all the compilation and then make /var/install-logs/install-log!
  +
   I recommend editing your install-log.rc right away and shaping it to match your
  -site.  For instance, if you don't use /usr/local, remove it.  Add /usr/etc and
  -/usr/var to EXCLUDE (install-log is not meant to track configuration and state
  -files, only binaries and support files that don't get touched beyond the
  -initial installation).  I strongly recommend that you add /usr/share/info/dir
  -to the EXCLUDE list; otherwise, /usr/share/info/dir will appear to belong to
  -every package that has an info page.
  +site.  For instance, if you don't use /usr/local, remove it from the file.
  +Add /usr/etc and /usr/var to EXCLUDE (install-log is not meant to track
  +configuration and state files, only binaries and support files that don't get
  +touched beyond the initial installation).  I strongly recommend that you add
  +/usr/share/info/dir to the EXCLUDE list; otherwise, /usr/share/info/dir will
  +appear to belong to every package that has an info page.
  +
  +Some of the above changes are already incorporated into the install-log.rc and
  +the compiled-in install-log defaults in versions newer than 1.9.
   
   +---------------------------+
     2. INSTALLING OTHER STUFF
  @@ -189,9 +212,9 @@
   shared between packages, like /usr/share/info/dir or a BSD-style init file.  It
   can't handle packages that install files with any timestamp other than "right
   now".  Sometimes you need to tweak its output a little bit, by touching the
  -installed files (see Linux example above), aging /var/install-logs/.timestamp, 
  -and/or editing the resultant log.  And you had better be sure of your
  -dependencies before you xargs rm something.
  +installed files, aging /var/install-logs/.timestamp, and/or editing the
  +resultant log.  And you had better be sure of your dependencies before you
  +xargs rm something.
   
   But nine times out of eight, it works.
   
  
  
  
-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe hints' in the subject header of the message



More information about the hints mailing list