public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zach Forrest <zach@disinformation.ca>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-user] portage revisited
Date: Fri, 15 Mar 2002 11:42:06 -0800	[thread overview]
Message-ID: <3C924E8E.70802@disinformation.ca> (raw)
In-Reply-To: Pine.LNX.4.21.0203151347130.26252-100000@lucifer.evil-core.com

I've written another function, epurge, that you can find in 
gentoo.completion that does some rudimentary dependency checking -- you 
might want to take a look at it.

I agree that major version numbers should be treated as separate 
packages (better yet I think they should be separate packages). For 
example, I would like to see media-libs/freetype be split into 
media-libs/freetype and media-libs/freetype2. I'm sure there has been 
discussion of this before (if so I don't mean to rehash an old 
discussion -- assuming that there was a resolution).

Zach

P.S. Hard coding is bad.

Bob Phan wrote:
> On Fri, 15 Mar 2002, Zach Forrest wrote:
> 
> 
>>The attached files should make this a little safer. I changed the grep 
>>commands a little, so as only to filter the exact packages that can have 
>>more than one version installed (e.g. "grep -v db" filters out more than 
>>just sys-libs/db). The script first runs the command with the 
>>"--pretend" flag, then asks for confirmation (after displaying the 
>>output of the emerge command), and finally proceeds (if that is your 
>>wish). Hope it helps.
>>
>>Zach
> 
> I like it, it's really slick. :)
> 
> The only problem I foresee, is that the list of packages is hardcoded.
> I think the only real way to get _real_ safe unmerging is for portage
> to treat major version numbers as separate packages or handle them in
> some special way.  I believe I heard word that dependancy checking will
> be done before an unmerge in the upcoming portage, so maybe that will
> solve the issue.
> 
> Anyway, thanks, it's great.
> 




  reply	other threads:[~2002-03-15 19:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3C910D3B.9010901@earthlink.net>
     [not found] ` <NDECLAINNBLNMIOCBPMPGEKLCDAA.adam-aig@attbi.com>
     [not found]   ` <20020314141051.69757313.rogan@fizbat.com>
2002-03-14 22:27     ` [gentoo-dev] Re: [gentoo-user] portage revisited Joshua Hansen
2002-03-14 23:44       ` Zach Forrest
2002-03-15  3:17         ` Joshua Hansen
2002-03-15  8:44           ` Bjarke Sørensen
2002-03-15  9:56       ` Bob Phan
2002-03-15 18:20         ` Zach Forrest
2002-03-15 13:52           ` Bob Phan
2002-03-15 19:42             ` Zach Forrest [this message]
2002-03-15 19:08         ` Frank Thieme

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=3C924E8E.70802@disinformation.ca \
    --to=zach@disinformation.ca \
    --cc=gentoo-dev@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