Re: [gentoo-user] see what's been emerged

2010-01-18 Thread Alex Schuster
James writes:

 All,
 
 I posted this question about a year ago and can't find the email or
 answer for the life of me...so I'll try again. :)

On 2009-06-28, the answer was this:
for f in `ls -rt \`find /var/db/pkg -name *.ebuild\``; do basename $f 
.ebuild; done

 I'm trying to find a file or database that keeps track of everything
 I've emerged since I set my system up, preferably in chronological
 order.
 
 Where / how can I obtain this information? I know that portage keeps
 track of it somehow.

It's all in /var/log/emerge.log, but the format is not very readable. 
Emerge app-portage/genlop, and try genlop -l.

 Mon Apr  6 20:35:28 2009  app-misc/screen-4.0.3
 Mon Apr  6 20:37:25 2009  sys-power/hibernate-script-1.97-r4
 Mon Apr  6 20:37:31 2009  sys-apps/tuxonice-userui-0.7.2
 Mon Apr  6 20:38:42 2009  sys-kernel/tuxonice-sources-2.6.24-r9
 Mon Apr  6 23:26:58 2009  app-arch/lzma-utils-4.32.7
 Mon Apr  6 23:27:52 2009  app-portage/eix-0.15.4
 ...

Wonko



Re: [gentoo-user] see what's been emerged

2010-01-18 Thread Anton Bobov
Hi.

On Mon, Jan 18, 2010 at 10:03:26 -0500, James wrote:
 I posted this question about a year ago and can't find the email or
 answer for the life of me...so I'll try again. :)
 
 I'm trying to find a file or database that keeps track of everything
 I've emerged since I set my system up, preferably in chronological
 order.
 
 Where / how can I obtain this information? I know that portage keeps
 track of it somehow.

You can use qlop --list which in app-portage/portage-utils.

-- 
Cheers,
Anton


pgpTXXcazvcOe.pgp
Description: PGP signature


Re: [gentoo-user] see what's been emerged

2010-01-18 Thread James
I guess I had deleted that email -- shame...many thanks for pulling up
the answer. I greatly appreciate it!

-j

On Mon, Jan 18, 2010 at 10:36 AM, Alex Schuster wo...@wonkology.org wrote:
 James writes:

 All,

 I posted this question about a year ago and can't find the email or
 answer for the life of me...so I'll try again. :)

 On 2009-06-28, the answer was this:
 for f in `ls -rt \`find /var/db/pkg -name *.ebuild\``; do basename $f
 .ebuild; done

 I'm trying to find a file or database that keeps track of everything
 I've emerged since I set my system up, preferably in chronological
 order.

 Where / how can I obtain this information? I know that portage keeps
 track of it somehow.

 It's all in /var/log/emerge.log, but the format is not very readable.
 Emerge app-portage/genlop, and try genlop -l.

     Mon Apr  6 20:35:28 2009  app-misc/screen-4.0.3
     Mon Apr  6 20:37:25 2009  sys-power/hibernate-script-1.97-r4
     Mon Apr  6 20:37:31 2009  sys-apps/tuxonice-userui-0.7.2
     Mon Apr  6 20:38:42 2009  sys-kernel/tuxonice-sources-2.6.24-r9
     Mon Apr  6 23:26:58 2009  app-arch/lzma-utils-4.32.7
     Mon Apr  6 23:27:52 2009  app-portage/eix-0.15.4
     ...

        Wonko



Re: [gentoo-user] see what's been emerged

2010-01-18 Thread James
Thanks Anton...much appreciated!

-j

On Mon, Jan 18, 2010 at 10:48 AM, Anton Bobov an...@bobov.name wrote:
 Hi.

 On Mon, Jan 18, 2010 at 10:03:26 -0500, James wrote:
 I posted this question about a year ago and can't find the email or
 answer for the life of me...so I'll try again. :)

 I'm trying to find a file or database that keeps track of everything
 I've emerged since I set my system up, preferably in chronological
 order.

 Where / how can I obtain this information? I know that portage keeps
 track of it somehow.

 You can use qlop --list which in app-portage/portage-utils.

 --
 Cheers,
 Anton



Re: [gentoo-user] see what's been emerged

2010-01-18 Thread Albert W. Hopkins
On Mon, 2010-01-18 at 10:03 -0500, James wrote:
 All,
 
 I posted this question about a year ago and can't find the email or
 answer for the life of me...so I'll try again. :)
 
 I'm trying to find a file or database that keeps track of everything
 I've emerged since I set my system up, preferably in chronological
 order.
 
 Where / how can I obtain this information? I know that portage keeps
 track of it somehow.

emerge.log, unless you (or a log rotator) have truncated it.