Hi, Thanks for the comments! (And excuses for this very late reply.) For the record: we're discussing this proposed patch for the Debian GNU/Linux FAQ (see Bug 342790): --------------- --- uptodate.sgml 10 Dec 2005 13:27:35 -0000 1.20 +++ uptodate.sgml 10 Dec 2005 13:38:14 -0000 @@ -209,10 +209,12 @@ <sect id="keepingalog">How can I keep a log of the packages I added to the system? -<p><prgn/dpkg/ keeps a record of the packages that have been unpacked, -configured, removed, and/or purged, but does not (currently) keep a log -of terminal activity that occurred while a package was being so manipulated. +<p>Passing the --log-option to <prgn/dpkg/ makes <prgn/dpkg/ log status +change updates and actions. + +<p><prgn/aptitude/ logs the package installations, removals, and upgrades that +it performs to <file>/var/log/aptitude</file>. + +<p>Another way to record your actions is to run your session within the <manref +name="script" section="1"> program. -<p>The simplest way to work around this is to run your -<prgn>dpkg</prgn>/<prgn>dselect</prgn>/<prgn>apt-get</prgn>/whatever -sessions within the <manref name="script" section="1"> program. --------------- Op ma 12 dec 2005 om 11:07:14 +0100 schreef Siward de Groot: > On Saturday 10 December 2005 23:41, Joost van Baal wrote: > > [...] > <snip lots of brainstorming-like comments> > > --------------------------------------------------------------------------- > Some more concrete remarks : > > You didn't change the section title. Hrm, I guess this one is better: "How can I keep a log of the packages I added to the system? I'd like to know when which package upgrades and removals have occured!" <snip> > +Passing the --log-option to dpkg makes dpkg log status change updates > + and actions. > Better quote '--log', i think. Yup, <tt>--log</tt>-option will look better. > What kind of 'actions' does it log ? only it's own actions ? I guess this is better: -------- <p>Passing the <tt>--log</tt>-option to <prgn/dpkg/ makes <prgn/dpkg/ log status change updates and actions. It logs both the <prgn/dpkg/-invokation (e.g. <example> 2005-12-30 18:10:33 install hello 1.3.18 2.1.1-4 </example> <p>) and the results (e.g. <example> 2005-12-30 18:10:35 status installed hello 2.1.1-4 </example> <p>) If you'd like to log all your <prgn/dpkg/ invokations (even those done using frontends like <prgn/aptitude/), you could add <example> log /var/log/dpkg.log </example> <p>to your <file>/etc/dpkg/dpkg.cfg</file>. More details on this can be found in the <manref name="dpkg" section="1"> manual page. -------- > To which file ? One has to supply the desired file on the dpkg commandline. > > +Another way to record your actions is to > + run your session within the script(1) program. > s/session/install-session/ ? > users might try to run their xsession in it otherwise :) I'll change that to "package management session". Thanks again, Bye, Joost
Attachment:
signature.asc
Description: Digital signature