public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Gaffney <agaffney@skylineaero.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] /etc/make.profile/use.defaults
Date: Wed, 12 May 2004 11:39:51 -0500	[thread overview]
Message-ID: <40A25357.2060707@skylineaero.com> (raw)
In-Reply-To: <200405130133.50828.jstubbs@gentoo.org>

Jason Stubbs wrote:
> On Thursday 13 May 2004 01:03, Pieter Van den Abeele wrote:
> 
>>>On 12 May 2004, at 17:44, Andrew Gaffney wrote:
>>>
>>>>But they are only 'scheduled for installation' if the USE flag is
>>>>activated. The '--emptytree' flag gets emerge in some weird 'chicken
>>>>and egg' situation. With '--emptytree' set, emerge should assume
>>>>nothing is installed. If nothing is installed, then tcl and tk aren't
>>>>installed and the 'tcltk' USE flag shouldn't be auto-activated.
>>>
>>>true, unless of course tcl and tk are in the world file, or some other
>>>installed package depends on both, and therefore causes the tcltk use
>>>flag to be triggered.
>>>but it should certainly not auto-enable the USE flag (if it isn't
>>>enabled specifically) because the current system has it enabled.
>>>--emptytree should assume nothing is installed
> 
> 
> This one, I'm undecided on. Strictly, --emptytree should assume nothing is 
> installed. In practice though, many users use it to reinstall everything. If 
> --emptytree does actually assume nothing is installed, users could find 
> themselves with blocked packages overwriting each other and wonderful things 
> like that.
> 
> Two options I see are:
> a) Keep current behaviour
> b) Make --emptytree a --pretend only option and create a new --reinstall.

I think it is more of a consistency bug than a function bug. I don't believe it 
causes any problems in practice, and I only stumbled across is because of the 
project I'm working on. I don't think it actually affects anyone.

-- 
Andrew Gaffney
Network Administrator
Skyline Aeronautics, LLC.
636-357-1548


--
gentoo-portage-dev@gentoo.org mailing list


  reply	other threads:[~2004-05-12 16:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12  3:02 [gentoo-portage-dev] building dependency tree Andrew Gaffney
2004-05-12  5:14 ` Pieter Van den Abeele
2004-05-12  6:42   ` Andrew Gaffney
2004-05-12  7:59     ` Pieter Van den Abeele
2004-05-12 14:43       ` Andrew Gaffney
2004-05-12 15:02         ` Pieter Van den Abeele
2004-05-12 15:14           ` [gentoo-portage-dev] /etc/make.profile/use.defaults (was: building dependency tree) Andrew Gaffney
2004-05-12 15:19             ` [gentoo-portage-dev] /etc/make.profile/use.defaults Andrew Gaffney
2004-05-12 15:43               ` Pieter Van den Abeele
2004-05-12 15:44                 ` Andrew Gaffney
2004-05-12 16:03                   ` Pieter Van den Abeele
2004-05-12 16:08                     ` Andrew Gaffney
2004-05-12 16:33                     ` Jason Stubbs
2004-05-12 16:39                       ` Andrew Gaffney [this message]
2004-05-12 17:28                         ` Jason Stubbs
2004-05-12 16:25 ` [gentoo-portage-dev] building dependency tree Jason Stubbs
2004-05-15  4:12   ` Andrew Gaffney
2004-05-15  6:14     ` Jason Stubbs
2004-05-15  6:50       ` Andrew Gaffney
2004-05-15  7:06         ` Jason Stubbs
2004-05-15 15:31           ` Andrew Gaffney

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=40A25357.2060707@skylineaero.com \
    --to=agaffney@skylineaero.com \
    --cc=gentoo-portage-dev@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