public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: R Hill <dirtyepic.sk@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Improved ebuild information
Date: Mon, 10 Oct 2005 13:23:29 -0600	[thread overview]
Message-ID: <dief3j$scs$1@sea.gmane.org> (raw)
In-Reply-To: <1128948829.8881.52.camel@cgianelloni.nuvox.net>

Chris Gianelloni wrote:

> Here's my question... use.local.desc is already package-specific, so why
> would we need yet *another* place to put package-specific definitions?
> Would it not be enough to have use.local.desc overlay on use.desc?  If
> package foo uses global USE flag bar in a way different from the
> description in use.desc, then it should list the USE flag in
> use.local.desc with the correct description for that package.

That's another good idea, and i think it could produce the same results. 
  The only downside I can think of is that use.local.desc wouldn't allow 
for version-specific flags.  But 'equery uses' already solves this as it 
only displays defs for the flags in the IUSE of the ebuild being 
queried.  The only case not covered is if the same flag is used in two 
versions of a package to mean different things, and i don't see that 
happening.

euse is a bit different, but still not a problem.  right now it does this:

   root ~ #  euse -i mozilla
   global use flags (searching: mozilla)
   ************************************************************
   [-    ] mozilla - Adds mozilla support

   local use flags (searching: mozilla)
   ************************************************************
   no matching entries found


it could do this instead:


   root ~ #  euse -i mozilla
   global use flags (searching: mozilla)
   ************************************************************
   [-    ] mozilla - Adds mozilla support

   local use flags (searching: mozilla)
   ************************************************************
   [-    ] mozilla (app-fake/fooapp):
   builds the optional mozilla browser plugin

   [-    ] mozilla (app-fake/someotherapp):
   use embedded mozilla engine to render newsfeeds in html

   [-    ] mozilla (app-fake/yetanotherapp):
   summon giant lizard to invade Tokyo


actually i just realized this already works with euse, no changes 
necessary. :D

thoughts/suggestions/kicksinthenuts? what other than equery would need 
to be fixed to recognize the overlay?  is there anything that would 
explicitly break if a USE flag was in both use.desc and use.local.desc?

--de.

-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2005-10-10 19:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-01 20:19 [gentoo-dev] Improved ebuild information Daniel Stiefelmaier
2005-10-01 20:22 ` Ciaran McCreesh
2005-10-02  0:10   ` Daniel Stiefelmaier
2005-10-02  6:06     ` Chris Gianelloni
2005-10-05 18:03   ` Martin Schlemmer
2005-10-05 18:34     ` Ciaran McCreesh
2005-10-05 21:13     ` [gentoo-dev] " R Hill
2005-10-10 12:53       ` Chris Gianelloni
2005-10-10 17:36         ` Bruno
2005-10-10 19:02           ` Apreche
2005-10-10 19:23         ` R Hill [this message]
2005-10-10 19:56           ` Thomas de Grenier de Latour
2005-10-01 20:25 ` [gentoo-dev] " Simon Stelling
2005-10-02  0:46   ` Daniel Stiefelmaier
2005-10-02  2:35     ` Alec Warner

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='dief3j$scs$1@sea.gmane.org' \
    --to=dirtyepic.sk@gmail.com \
    --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