On 10/18/07, Travis Willard <travis@archlinux.org> wrote:
On Thu, 18 Oct 2007 10:36:37 -0500, Aaron Griffin wrote
What about putting it in the local DB entry for each package? /var/lib/pacman/local/screen/install.log ?
-1
While that associates it nicely with its related package, I don't really like the idea of users needing to traipse through their local DB to get the logs - what if at some point in the future we decide to change DB formats, say from filesystem to database, for example?
IMO /var/log is the place for logs like this. If you want to separate it by package, then /var/log/pacman/{pkgname}/install.log could work, or some variant thereof, or we could just jam it all into one file and have delineations, like
--------- Installed libfoo, 01/01/1901 ------------ ==> Warning: Libfoo needs libbar to support foobar functionality. ==> pacman -S libbar to get it. --------- Installed kernel26, /01/01/1901 ---------- ==> Generating mkinitcpio crap... blah blah blah ==> Done.
And so on.
Yeah /var/log is a much better place - moreover I was trying to suggest the "one log file per package" but I don't know how good of an idea that is. I actually kinda like Travis' format above with the delimiter there.