public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Depclean and cross-foo/gcc
Date: Fri, 19 Oct 2007 10:50:05 -0700	[thread overview]
Message-ID: <4718EE4D.8020100@gentoo.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0710191148170.32497@iabervon.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Daniel Barkalow wrote:
> I've been doing a lot of --depclean lately, and I've run into something 
> odd. "emerge --depclean cross-avr/gcc" wants to remove all 3 versions, but 
> it's in my world file. On the other hand, "emerge --depclean" doesn't want 
> to remove any of them. I initially set this up with a crossdev that's now 
> quite ancient, which may be significant, but I don't want to entirely redo 
> all my avr compilers to get them with the new crossdev.
> 
> What I'd actually like is to have a specific version (the one that our 
> code is most heavily tested with), and the latest version (to test that). 
> Is there some way to have --depclean see a dependancy on a specific 
> version (or slot, as I've already masked other versions that would be in 
> that slot) from world or the equivalent?

I think you want --prune, since --depclean behaves like a dependency
aware version of --unmerge.

Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFHGO5L/ejvha5XGaMRAuErAJ9X9fs1gK2Iyp2G9gvJlBf8Da0VwACgl/iQ
ZCYrEPK4lkhxwG4hGPBN+N4=
=yQOh
-----END PGP SIGNATURE-----
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-10-19 18:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19 16:21 [gentoo-user] Depclean and cross-foo/gcc Daniel Barkalow
2007-10-19 17:50 ` Zac Medico [this message]
2007-10-19 22:18   ` Daniel Barkalow
2007-10-19 23:14     ` Zac Medico

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=4718EE4D.8020100@gentoo.org \
    --to=zmedico@gentoo.org \
    --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