public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Hampicke <mgehampicke@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] GCC upgrade from 4.5.3 to 4.5.4 automatically removes 4.5.3???? Wtf???
Date: Sat, 8 Sep 2012 01:32:34 +0200	[thread overview]
Message-ID: <CADPZhuoUcNbwzU4E9CABr1JTb_NGRSnv+Yo=oiHSU7z4g=Ob_g@mail.gmail.com> (raw)
In-Reply-To: <20120907235921.5ae1d80c@digimed.co.uk>

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

2012/9/8 Neil Bothwick <neil@digimed.co.uk>

> On Fri, 07 Sep 2012 23:14:05 +0200, Michael Hampicke wrote:
>
> > >> genlop -ul | grep 'sys-devel/gcc-[0-9]'
> > >
> > > And this week's prize for unnecessary use of pipes and grep goes to...
> > >
> > > genlop -u sys-devel/gcc
>
> > Nope, we not only need the time when gcc was unmerged (-u), but also
> > when it was merged (-l). When there's little time difference between
> > merge and unmerge we can assume, that portage auto-cleaned the old
> > version of gcc. If you combine -u and -l you need to grep (to be exact
> > sys-devel/gcc-[0-9], because of sys-devel/gcc-config and
> > sys-devel/gcc-apple).
>
> genlop, unlike qlop, does exact matching by default, so gcc mtches only
> gcc, not gcc-config (use -s if you want that). When you give a package
> name all merges are shown by default (-l is to show the full
> history), so the command I gave does what you want, like this
>
>      Thu Jun 21 01:45:05 2012 <<< sys-devel/gcc-4.5.3-r2
>      Thu Jun 21 01:45:33 2012 >>> sys-devel/gcc-4.5.3-r2
>      Mon Jul 16 10:30:01 2012 <<< sys-devel/gcc-4.5.3-r2
>      Mon Jul 16 10:30:32 2012 >>> sys-devel/gcc-4.5.4
>      Thu Sep  6 11:24:27 2012 <<< sys-devel/gcc-4.6.3
>      Thu Sep  6 11:24:45 2012 >>> sys-devel/gcc-4.6.3
>      Thu Sep  6 11:26:15 2012 <<< sys-devel/gcc-4.5.4
>      Thu Sep  6 11:26:43 2012 >>> sys-devel/gcc-4.5.4
>
> Except it is coloured by default when outputting to a terminal, merges in
> green, unmerges in red. Using -l and then grep is saying "show me
> everything, oh no, cut out anything that's not gcc" rather than "show me
> all gcc merges and unmerges".
>
>
I tried your command before answering you - so I don't look like a fool :)
And I am 100% certain that genlop -u <package> only showed unmerges when I
tested it on my workstation (that's the reason I added -l | grep). However,
just now I tested it again on my notebook, and it works like you described
it (and like how you would expect it to work). Have to try it again on my
WS on monday.

Anyhoo, my point was to show the OP how he could check for himself that
portage always unmerges older packages when upgrading to newer versions in
the same slot - and for that, both solutions work.

Going to bed now

[-- Attachment #2: Type: text/html, Size: 2899 bytes --]

  reply	other threads:[~2012-09-07 23:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 11:24 [gentoo-user] GCC upgrade from 4.5.3 to 4.5.4 automatically removes 4.5.3???? Wtf??? Tanstaafl
2012-09-07 11:40 ` Neil Bothwick
2012-09-07 11:41 ` [gentoo-user] " Nikos Chantziaras
2012-09-07 11:44 ` [gentoo-user] " Markos Chandras
2012-09-07 12:53   ` Tanstaafl
2012-09-07 13:00     ` Michael Mol
2012-09-07 13:12     ` Markos Chandras
2012-09-07 14:27       ` Tanstaafl
2012-09-07 14:58         ` Paul Hartman
2012-09-07 13:22     ` Markos Chandras
2012-09-07 14:29       ` Tanstaafl
2012-09-07 14:44         ` Michael Mol
2012-09-07 14:25     ` [gentoo-user] " Grant Edwards
2012-09-07 17:26     ` [gentoo-user] " Michael Hampicke
2012-09-07 19:52       ` Neil Bothwick
2012-09-07 21:14         ` Michael Hampicke
2012-09-07 22:59           ` Neil Bothwick
2012-09-07 23:32             ` Michael Hampicke [this message]
2012-09-08 15:06 ` James Cloos

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='CADPZhuoUcNbwzU4E9CABr1JTb_NGRSnv+Yo=oiHSU7z4g=Ob_g@mail.gmail.com' \
    --to=mgehampicke@gmail.com \
    --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