public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Terje Kvernes <terjekv@math.uio.no>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] IUSE variable clarification
Date: 08 Jan 2003 20:18:47 +0100	[thread overview]
Message-ID: <wxxvg0zxxew.fsf@nommo.uio.no> (raw)
In-Reply-To: <20030108090422.A21048@twobit.net>

Nick Jones <carpaski@twobit.net> writes:

> It should contain _EVERY_ reference you make to a USE variable. So
> if you check ncurses, it contains ncurses... if you check gtk, it
> contains gtk. It's presently unused, but required for upcoming
> features like rebuild-on-use-change.

  isn't the IUSE-variable really redundant?  shouldn't portage be able
  to get the USE-flags directly from the ebuilds DEPEND-statement
  without adding an IUSE-kludge?  as far as I can tell IUSE just moves
  the work of maintaining this list from portage to the ebuild
  maintainer, who now has to update both DEPEND and IUSE.

  there is no doubt that portage needs the functionality IUSE
  provides, I'm just sceptical to the way that functionality is being
  provided.

-- 
Terje

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-01-08 19:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 14:31 [gentoo-dev] IUSE variable clarification Burton Samograd
2003-01-08 14:59 ` Maik Schreiber
2003-01-09 16:44   ` Burton Samograd
2003-01-09 17:00     ` [gentoo-dev] " Wilbert Berendsen
2003-01-09 17:05       ` Maik Schreiber
2003-01-09 17:06       ` Yannick Koehler
2003-01-09 17:03     ` [gentoo-dev] " Maik Schreiber
2003-01-08 15:04 ` Nick Jones
2003-01-08 19:18   ` Terje Kvernes [this message]
2003-01-08 19:52     ` Felipe Ghellar
2003-01-08 20:11       ` Terje Kvernes
2003-01-09 15:42     ` Paul de Vrieze
2003-01-09 21:05       ` Bob Phan
2003-01-09 22:35         ` Paul de Vrieze
2003-01-10 12:28           ` Bob Phan

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=wxxvg0zxxew.fsf@nommo.uio.no \
    --to=terjekv@math.uio.no \
    --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