Re: Logging what got installed

On Tue, May 12, 2015 at 02:21:23AM +0100, Ken Moffat wrote:
> TLDR; : logging what gets installed or updated can be painful
> 
more than I thought!
> 
> Seems to work, so my logging must now be 110% correct ;-)
> 
except that when I used it to build LFS, the output for coreutils
missed a lot of programs (the few in /bin that had been symlinked to
/tools were accounted for, but other new entries such as chmod
disappeared.
> 
> Anyway, for a normal build the diff of the before and after logs was
> ok, after I had sorted out exactly what to do (trad diff: 'c'
> records to change 1 or many lines [1], deletions[2], '---'[3],
> additions [4] ; other a or d headers [5]; additions [6] or deletions
> [7] - processes listed below.
> 
'diff' is set to produce the minimal changes needed to convert one
version of a file to another.  The 'c' records for many lines can
include a block - in this case more lines were added than removed.

I'm still exploring this, and I can see a few possible solutions
(apart from writing a C program!), but the elapsed time might be
interesting.  Probably, 'comm' (which needs 'sort -n') will be
involved.  After finding that bug, I think I'll let this thread die,
it is becoming too embarassing.

ĸen
-- 
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
-- 
http://lists.linuxfromscratch.org/listinfo/lfs-chat
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page