public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: A Gentoo Enema
Date: Fri, 23 Dec 2005 18:38:20 +0000	[thread overview]
Message-ID: <20051223183820.70657d00@hactar.digimed.co.uk> (raw)
In-Reply-To: <878xub3ct0.fsf@newsguy.com>

[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]

On Fri, 23 Dec 2005 12:09:47 -0600, reader@newsguy.com 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 against
> > as an argument to the script. Sorry, I should have made that clear.
> 
> Why would you trim off the date info?

To pass to genlop with --date, in order to get a list of all packages
installed after that date.
 
> With your find approach, if the package has been uninstalled you'll
> find nothing.  

Of course. The question was about finding all packages installed after a
particular reference package, in this case gcc. If the reference package
is no longer installed 9impossible with gcc of course) the question
becomes pointless.

> If you were wanting to know if some other behaviour could be dated to
> the uninstall of something it would be of no use.

It would, you'd only have to modify it to use genlop's -u option.

All of this is irrelevant anyway, using genlop and parsing the output is
going round three sides of a square instead of going in a straight line
with find. Using a non-standard bash or perl script to parse the output
of an optional perl script seems rather redundant when you can do it all
with one call to a core command.


-- 
Neil Bothwick

After a few years in space, even Worf started to look good...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-12-23 18:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-17  5:24 [gentoo-user] A Gentoo Enema Tom Eastman
2005-12-17  5:45 ` [gentoo-user] " Tom Eastman
2005-12-17 10:04   ` Neil Bothwick
2005-12-22 14:52     ` Iain Buchanan
2005-12-22 19:32       ` Neil Bothwick
2005-12-22 21:37         ` reader
2005-12-22 22:59           ` Neil Bothwick
2005-12-23  0:32             ` reader
2005-12-23  7:47               ` Neil Bothwick
2005-12-23 15:15                 ` reader
2005-12-23 17:06                   ` Neil Bothwick
2005-12-23 18:09                     ` reader
2005-12-23 18:38                       ` Neil Bothwick [this message]
2005-12-23 15:17                 ` reader
2005-12-23 17:04                   ` Neil Bothwick
2005-12-17  6:02 ` [gentoo-user] " Steven Ringwald
2005-12-17  6:45 ` Willie Wong
2005-12-17  7:23 ` Richard Fish
2005-12-17  9:49 ` Neil Bothwick
2005-12-17 12:29 ` [gentoo-user] " reader
2005-12-17 20:00   ` Tom Eastman
2005-12-18 11:23   ` Neil Bothwick
2005-12-18 13:46     ` Michael Crute
2005-12-18 20:58     ` reader
  -- strict thread matches above, loose matches on Subject: below --
2005-12-23  4:42 Beau E. Cox
2005-12-23  7:25 ` Neil Bothwick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051223183820.70657d00@hactar.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox