On Fri, 23 Dec 2005 12:09:47 -0600, [EMAIL PROTECTED] wrote:
> >> > genlop --list --date "$(genlop --nocolor $1 | grep $1 | tail -n 1 |
> >> > sed 's/^ *\(.*\) >>>.*/\1/')"
> >>
> >> What is it supposed to do? Here it gets genlops usage message.
> >
> > you need to give the name of the package y
Neil Bothwick <[EMAIL PROTECTED]> writes:
> On Fri, 23 Dec 2005 09:15:31 -0600, [EMAIL PROTECTED] wrote:
>
>> > genlop --list --date "$(genlop --nocolor $1 | grep $1 | tail -n 1 |
>> > sed 's/^ *\(.*\) >>>.*/\1/')"
>>
>> What is it supposed to do? Here it gets genlops usage message.
>
> you need
On Fri, 23 Dec 2005 09:15:31 -0600, [EMAIL PROTECTED] wrote:
> > genlop --list --date "$(genlop --nocolor $1 | grep $1 | tail -n 1 |
> > sed 's/^ *\(.*\) >>>.*/\1/')"
>
> What is it supposed to do? Here it gets genlops usage message.
you need to give the name of the package you want to compare
On Fri, 23 Dec 2005 09:17:37 -0600, [EMAIL PROTECTED] wrote:
> > What's wrong with using a simple find command as I originally posted?
>
> Do you mean run against / or what?
Against /var/db/pkg, where you'll find everything you have installed,
complete with datestamps. See my first post in this
Neil Bothwick <[EMAIL PROTECTED]> writes:
> What's wrong with using a simple find command as I originally posted?
Do you mean run against / or what?
--
gentoo-user@gentoo.org mailing list
Neil Bothwick <[EMAIL PROTECTED]> writes:
> genlop --list --date "$(genlop --nocolor $1 | grep $1 | tail -n 1 | sed 's/^
> *\(.*\) >>>.*/\1/')"
What is it supposed to do? Here it gets genlops usage message.
--
gentoo-user@gentoo.org mailing list
On Thu, 22 Dec 2005 18:32:23 -0600, [EMAIL PROTECTED] wrote:
> > Yes, but then you'd have to do some funky regexp stuff to find the
> > last line showing gcc (in this case) and only show the lines after
> > it. It was a lot easier to do this with find -newer.
>
> Here is a pooryly coded sloppy pe
On Thu, 22 Dec 2005 18:42:38 -1000, Beau E. Cox wrote:
> I have a small perl script, 'echanges', that determines the latest
> timestamp for installed packages; I find it very helpful to determine
> what my daily cron of 'emerge -uD world' has done. I will post it
> here if there is any interest;
Hi reader -
At 2005-12-22, 11:37:35 you wrote:
>Neil Bothwick <[EMAIL PROTECTED]> writes:
>
>> On Fri, 23 Dec 2005 00:22:24 +0930, Iain Buchanan wrote:
>>
>>> > find /var/db/pkg -name '*.ebuild' !
>>> > -newer /var/db/pkg/sys-devel/gcc-3.4.4-r1/gcc-3.4.*
>>> >
>>> > to find all packages compile
Neil Bothwick <[EMAIL PROTECTED]> writes:
> On Thu, 22 Dec 2005 15:37:35 -0600, [EMAIL PROTECTED] wrote:
>
>> > genlop is really nice, I use it all the time, but I don't think it
>> > has an option to find all packages installed after a particular
>> > package. It would be a nice variation on the
On Thu, 22 Dec 2005 15:37:35 -0600, [EMAIL PROTECTED] wrote:
> > genlop is really nice, I use it all the time, but I don't think it
> > has an option to find all packages installed after a particular
> > package. It would be a nice variation on the --date option.
>
> Isn't the output in chrono or
Neil Bothwick <[EMAIL PROTECTED]> writes:
> On Fri, 23 Dec 2005 00:22:24 +0930, Iain Buchanan wrote:
>
>> > find /var/db/pkg -name '*.ebuild' !
>> > -newer /var/db/pkg/sys-devel/gcc-3.4.4-r1/gcc-3.4.*
>> >
>> > to find all packages compiled before your last compiler update.
>>
>> There's also ap
On Fri, 23 Dec 2005 00:22:24 +0930, Iain Buchanan wrote:
> > find /var/db/pkg -name '*.ebuild' !
> > -newer /var/db/pkg/sys-devel/gcc-3.4.4-r1/gcc-3.4.*
> >
> > to find all packages compiled before your last compiler update.
>
> There's also app-portage/genlop, quite nice for doing various thing
On Sat, 2005-12-17 at 10:04 +, Neil Bothwick wrote:
> On Sat, 17 Dec 2005 18:45:24 +1300, Tom Eastman wrote:
>
> > It would be cool if you could list every package based on when it was
> > installed... so the stuff that is *reall* old can be freshened by a
> > re-installation (with whatever my
Neil Bothwick <[EMAIL PROTECTED]> writes:
> There are some major advantages to not re-installing. One is that all
> your settings remain untouched, whereas a reinstall requires you to
> reconfigure everything.
Neil,
You're going to have to slow down on all these usefull posts. I keep
lots of s
On 12/18/05, Neil Bothwick <[EMAIL PROTECTED]> wrote:
> On Sat, 17 Dec 2005 06:29:41 -0600, [EMAIL PROTECTED] wrote:
>
>
> > > So what I want to do is give my computer a complete clean-out. What I
> > > really CAN'T be bothered doing is a complete format and re-install!
>
> There are some major ad
On Sat, 17 Dec 2005 06:29:41 -0600, [EMAIL PROTECTED] wrote:
> > So what I want to do is give my computer a complete clean-out. What I
> > really CAN'T be bothered doing is a complete format and re-install!
> What you've described and what others have posted sounds more
> compiicated and time c
[EMAIL PROTECTED] wrote:
> What you've described and what others have posted sounds more
> compiicated and time consuming than doing what you CAN'T be bothered
> with. Also allows the opportunity to redo any partitioning scheme
> and swap setup that may have aged or not fill the bill any more.
*
Tom Eastman <[EMAIL PROTECTED]> writes:
> So what I want to do is give my computer a complete clean-out. What I
> really CAN'T be bothered doing is a complete format and re-install!
What you've described and what others have posted sounds more
compiicated and time consuming than doing what you C
On Sat, 17 Dec 2005 18:45:24 +1300, Tom Eastman wrote:
> It would be cool if you could list every package based on when it was
> installed... so the stuff that is *reall* old can be freshened by a
> re-installation (with whatever my current compiler is)
How about
find /var/db/pkg -name '*.ebuild
Also on the subject of cleaning things out and keeping things somewhat
up-to-date... what do you suppose would be a good way of seeing how old
some packages are on your system?
It would be cool if you could list every package based on when it was
installed... so the stuff that is *reall* old can b
21 matches
Mail list logo