public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Holly Bostick <motub@planet.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] package conflict on update
Date: Sat, 07 Jan 2006 03:00:37 +0100	[thread overview]
Message-ID: <43BF20C5.8040107@planet.nl> (raw)
In-Reply-To: <9b1675090601051848u69fd415nd6fe37bcb5bb96e2@mail.gmail.com>

Trenton Adams schreef:
> On 1/5/06, Neil Bothwick <neil@digimed.co.uk> wrote:
> 
>>On Thu, 5 Jan 2006 16:32:20 -0700, Trenton Adams wrote:
>>
>>
>>>>something like
>>>>
>>>>if_blocked_by('openmotif')
>>>>        ewarn "You must unmerge openmotif before proceeding"
>>>
>>>Yes, or as follows...
>>>
>>>if_blocked_by('openmotif')
>>>  auto_unmerge('openmotif')
>>>  # continue with merge which should automatically be merging openmotif
>>>anyhow.
>>
>>Absolutely not! I don't want portage removing something I may be using at
>>the time without my saying so.
> 
> 
> Good point.  Perhaps it should ask then?
> 
> 

Well, it does, by stopping and waiting for you to perform an action and
either restart the stopped process (if the action you took was to
unmerge the blocking package), or to forego the stopped process
entirely,  if you choose not to remove the blocked package because you
want to keep it for whatever reason (it could happen).

You're assuming that unmerging the blocking package is *always* the
right solution for everyone at all times (in this case, it's not really
relevant, since motif-config will itself re-install openmotif), but the
point of Gentoo is that you are in control. If I am in control, then I
have to decide what I want done in each particular situation that
occurs, which is exactly what I have to do with the current setup-- very
obviously, since Portage will stop until I make a decision and act on
it. So fine, your new updated Portage informs me there's a block, and
says, "I could do this to solve it, shall I?" I myself am going to say
"no", because I want to know the nature of the block, and how Portage's
proposed action is going to affect the system that I have carefully
customized to my individual needs.

So I'm right in the same position as I was anyway; the emerge is stopped
(because I said, no don't go on with whatever you plan), and I'm off
reading ChangeLogs and the like to see what's going on in the
environment I'm suddenly dealing with. I suppose that it's all very nice
to have some extra dialog as if Portage was communicating with me more
"humanely", but it's just cosmetic, in actual fact.

Of course, that may be because I take time to read some of the
comprehensive documentation that so many have taken the time to write,
so I know what a Blocked Package is, so it doesn't freak me out when I
come across one. So sue me and call me names... oh wait, you had your
rant already. We'll mark that item "Done", then.

Ultimately, I'm sure such an extra dialog would be a nice thing, but I
don't so much see it as something to get all riled up about. Maybe it's
just me.

Holly


-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-01-07  2:13 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-05  7:29 [gentoo-user] package conflict on update Trenton Adams
2006-01-05  7:32 ` [gentoo-user] " Trenton Adams
2006-01-05 11:10 ` [gentoo-user] " Tom Martin
2006-01-05 11:25   ` Trenton Adams
2006-01-05 11:35     ` Holly Bostick
2006-01-05 11:41   ` Neil Bothwick
2006-01-05 15:16     ` Devon Miller
2006-01-05 16:08     ` Tom Martin
2006-01-05 16:14       ` Richard Fish
2006-01-05 17:51       ` Neil Bothwick
2006-01-05 23:43         ` Trenton Adams
2006-01-05 23:54         ` Trenton Adams
2006-01-06  0:56           ` Richard Fish
2006-01-06  2:51             ` Trenton Adams
2006-01-05 23:32     ` Trenton Adams
2006-01-06  0:16       ` Neil Bothwick
2006-01-06  2:48         ` Trenton Adams
2006-01-07  2:00           ` Holly Bostick [this message]
2006-01-07  4:35             ` Trenton Adams
2006-01-07  5:13             ` Trenton Adams
2006-01-07 12:51               ` Holly Bostick
2006-01-07 16:33                 ` Trenton Adams
2006-01-07 14:16               ` Abhay Kedia
2006-01-07 16:30                 ` Trenton Adams
2006-01-07 19:17                   ` Abhay Kedia
2006-01-07 21:55                     ` Trenton Adams
2006-01-08  0:12                       ` Holly Bostick
2006-01-08  1:06                         ` Trenton Adams
2006-01-08  1:08                           ` Trenton Adams
2006-01-08  8:10                           ` Abhay Kedia
2006-01-08  8:27                             ` Trenton Adams
2006-01-08  8:49                               ` Abhay Kedia
2006-01-08  9:03                                 ` Trenton Adams
2006-01-08  9:23                                   ` Abhay Kedia
2006-01-08  9:58                                     ` Trenton Adams
2006-01-08  8:02                       ` Abhay Kedia
2006-01-08  8:23                         ` Trenton Adams
2006-01-08 15:14                           ` Ernie Schroder
2006-01-08 20:58                             ` Trenton Adams
2006-01-09  7:07                               ` Abhay Kedia
2006-01-10  3:21                                 ` Ernie Schroder
2006-01-06  1:14     ` Zac Medico
2006-01-06  7:27       ` Abhay Kedia
2006-01-06  9:09         ` Neil Bothwick
2006-01-06  9:13       ` Neil Bothwick
2006-01-07  4:55         ` Trenton Adams

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=43BF20C5.8040107@planet.nl \
    --to=motub@planet.nl \
    --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