From: Bruno <bonbons67@internet.lu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Improved ebuild information
Date: Mon, 10 Oct 2005 19:36:57 +0200 [thread overview]
Message-ID: <200510101936.57255.bonbons67@internet.lu> (raw)
In-Reply-To: <1128948829.8881.52.camel@cgianelloni.nuvox.net>
On Monday 10 October 2005 14:53, 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.
>
The additionnal info about USE flags should not be what is this or that USE
flag used differently for, but rather what *exactly* does the use-flag
influence. What exact features of the program are enabled/disabled/changed by
the given USE flag.
Some USE flags are used to either compile against a lib that's shipped with a
package or with the system version of that lib. Would be useful to know.
Then there are USE flags like static which are very unprecise. Do they mean
that the program is 100% stand-alone (e.g. does not link against any lib) or
does it have to do with *.a, *.la files being installed, or just reduce the
count of libs linked against...
In addition, providing the info in the package metadata is cleaner as
information about a given package is in one place, and there is not one file
with 1k lines with many USE flags and their use for each and every package.
The aim is to allow to know what happens without reading the ebuild AND the
configure script and makefiles of a package.
Bruno
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-10 17:41 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 [this message]
2005-10-10 19:02 ` Apreche
2005-10-10 19:23 ` R Hill
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=200510101936.57255.bonbons67@internet.lu \
--to=bonbons67@internet.lu \
--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