public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Spider <spider@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Portage suggestion
Date: Fri, 13 Feb 2004 14:46:01 +0100	[thread overview]
Message-ID: <20040213144601.748e003e.spider@gentoo.org> (raw)
In-Reply-To: <20040213130332.GJ64670@james.is.never.wrong.nu>

[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]

begin  quote
On Fri, 13 Feb 2004 13:03:32 +0000
James Harlow <james@is.never.wrong.nu> wrote:


> > Here's the point,  we can easly remove the dependency on esd, and if
> > the code works, okay.  However, then you have an untracked
> > dependency when esd -is- installed but set as USE="-esd" , as it
> > will be needed, but not listed as such.


 
> Sure. I'm implicitly assuming that the --without-esd ./configure
> switch does the right thing, which obviously needs to be tested. But
> it's a pretty simple test.
> 
> That's what you were referring to, right?

No, if that isn't used its a simple thing to add a USE flag.  The issue
is with things that go...
"do I have alsa?  no...  not building alsa interface"
"do I have esound? no .. not building esound interface"   


without a choice to -disable (or enable) such things, when you can state
USE="-*" and then still get everything included, no dependencies tracked
and a hosed system when you finally try to live without alsa+esound.

too many builds use auto* functions like that, and no. "dynamic
dependencies" isn't a solution here either.   Metal hacking configure.*
is however one.


//Spider

-- 
begin  .signature
Tortured users / Laughing in pain
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2004-02-13 13:46 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 12:24 [gentoo-dev] Portage suggestion Timo Lindemann
2004-02-13 12:44 ` James Harlow
2004-02-13 12:54   ` Spider
2004-02-13 13:03     ` James Harlow
2004-02-13 13:10       ` Patrick Kursawe
2004-02-13 13:29         ` Paul de Vrieze
2004-02-13 13:31         ` James Harlow
2004-02-13 13:46       ` Spider [this message]
2004-02-13 14:05         ` Paul de Vrieze
2004-02-13 13:04     ` Paul de Vrieze
2004-02-13 17:29   ` Kumba
2004-02-13 12:46 ` neuron
2004-02-13 12:48 ` neuron
2004-02-13 12:53 ` Paul de Vrieze
2004-02-13 12:53 ` Ciaran McCreesh
2004-02-13 12:54 ` Patrick Kursawe
2004-02-13 12:58 ` Bartosch Pixa
2004-02-13 17:45 ` Mike Frysinger
2004-02-14 18:28 ` foser
2004-02-14 18:54   ` Thomas de Grenier de Latour
2004-02-14 18:59     ` Mike Frysinger
2004-02-14 19:01     ` Spider
  -- strict thread matches above, loose matches on Subject: below --
2002-12-15 18:23 [gentoo-dev] portage suggestion Jean-Francois Patenaude
2002-12-15 18:26 ` Mike Frysinger
2002-08-13 14:44 [gentoo-dev] Portage suggestion Mezei Zoltan
2002-08-13 15:09 ` Dan Naumov
2002-08-13 15:27   ` Mezei Zoltan
2002-08-13 16:11     ` Christian Skarby
2002-08-13 16:10       ` Thomas T. Veldhouse
2002-08-14  1:57         ` Charles Lacour
2002-08-13 16:24       ` Christian Skarby
2002-08-13 15:27   ` Hannes Mehnert

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=20040213144601.748e003e.spider@gentoo.org \
    --to=spider@gentoo.org \
    --cc=gentoo-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