public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Robert Cernansky <hslists2@zoznam.sk>
To: gentoo-user@lists.gentoo.org
Subject: Re[4]: [gentoo-user] xorg-x11 screwup
Date: Tue, 04 Jul 2006 19:44:54 +0200	[thread overview]
Message-ID: <Mahogany-0.66.0-12743-20060704-194454.00@kihnet.sk> (raw)
In-Reply-To: <1152033099.6231.6.camel@localhost.localdomain>

On Tue, 04 Jul 2006 19:11:39 +0200 Alan McKinnon <alan@linuxholdings.co.za> wrote:

AM> On Tue, 2006-07-04 at 18:29 +0200, Robert Cernansky wrote:
AM> > 
AM> > Hmm, it can be done with "garbage collector principe". Each
AM> > package will have counter which increases when some package which
AM> > depend on
AM> > it is installed. Decreased, when the package is uninstalled. If
AM> > counter is
AM> > zero, "dependency" package can be uninstalled along with package
AM> > specified
AM> > for uninstalling.
AM> 
AM> No, that still doesn't work. When the user unmerges kde-meta, with your
AM> proposal it will unmerge X11. The next step is that the user emerges
AM> gnome which first emerges X11 back again. This isn't so bad with a
AM> binary distro if the packages are on a CD, but on gentoo it's murder.
AM> 

Yes, you are right. I did not consider this practical issue.

AM> The only sane thing to do is to emerge dependencies when required and
AM> unmerge only thinks specifically asked for to be unmerged. You can't
AM> even reliably prompt the user with a dialog that says "The following
AM> dependencies of the package about to be unmerged are needed by no other
AM> package. Shall they be unmerged?" because of deep dependencies.
AM> Reverse constructing a multi-node tree and applying logic to it is no
AM> joke, hence the wise decision to have portage ignore this amazingly
AM> efficient bug-injecting process.

Yes, its not so easy, i see now. ;-) Like Bo Andresen wrote --depclean is the
best way.

Robert


-- 
Robert Cernansky
E-mail: hslists2@zoznam.sk
Jabber: HS@jabber.sk

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-07-04 17:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-02 15:24 [gentoo-user] xorg-x11 screwup Matthew R. Lee
2006-07-02 19:19 ` Donnie Berkholz
2006-07-02 20:17   ` Bo Ørsted Andresen
2006-07-02 20:24     ` Donnie Berkholz
2006-07-02 20:29       ` Bo Ørsted Andresen
2006-07-02 23:05       ` W.Kenworthy
2006-07-03  3:31         ` Nick Rout
2006-07-03  5:30         ` Graham Murray
2006-07-03  7:12           ` Donnie Berkholz
2006-07-03 21:37           ` Nick Rout
2006-07-04 16:29             ` Re[2]: " Robert Cernansky
2006-07-04 16:54               ` Bo Ørsted Andresen
2006-07-04 17:11               ` Re[2]: " Alan McKinnon
2006-07-04 17:44                 ` Robert Cernansky [this message]
2006-07-04 20:45                 ` Neil Bothwick
2006-07-05  3:37                   ` Nick Rout
2006-07-05  7:52                     ` Neil Bothwick
2006-07-02 20:39   ` Bo Ørsted Andresen
2006-07-02 20:53     ` Donnie Berkholz
2006-07-02 21:00       ` Bo Ørsted Andresen
2006-07-02 21:39         ` Matthew R. Lee
2006-07-02 21:45           ` Donnie Berkholz
2006-07-02 22:01           ` Bo Ørsted Andresen
2006-07-03 22:22           ` Matthew R. Lee

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=Mahogany-0.66.0-12743-20060704-194454.00@kihnet.sk \
    --to=hslists2@zoznam.sk \
    --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