On Sunday 02 October 2005 01:08, Daniel Stiefelmaier wrote:
On Saturday 01 October 2005 14:17, Jason Stubbs wrote:
This should go to [EMAIL PROTECTED] as ebuild developers are the ones that
decide what USE flags are available and how they're documented.
Of course they decide what flags are
I thought of a command like emerge mozilla-firefox --useinfo
that prints what each flag is good for. Maybe some are explained in 5
words, other may need 5 lines.
Personally, I think that this has only become necessary because USE flags are
overloaded too much and usually encompass an
Hi,
Daniel Stiefelmaier wrote:
Take the USE flag perl, for example. It has the description Adds
support/bindings for the Perl language. but for mysql setting it
enables the installation of some support scripts that just happen to
be written in perl.
Since perl is a global use flag, this is
man emerge provides information on possible options, why should there
not be a way to get information on an ebuilds option???
because emerge is the tool, not the object. You wouldn't expect the
openoffice documentation to cover examples for different kinds of
letters, would you?
err.. i
On Sat, Oct 01, 2005 at 11:57:01PM +0200, Daniel Stiefelmaier wrote:
man emerge provides information on possible options, why should there
not be a way to get information on an ebuilds option???
because emerge is the tool, not the object. You wouldn't expect the
openoffice
Jamming a 'built-in list of use flags' into ebuilds/metadata.xml first
of all is vague,
I tried to explain simon that i don't want to have the explanations
built into the emerge-programm, because i thought he understood me that way.
second of all is going to jack up the tree's size,
i
On Saturday 01 October 2005 14:01, Daniel Stiefelmaier wrote:
I'd like to introduce two ideas i had to improve portage.
I haven't had an idea introduced to me that was new for at least a year..
Patches are more interesting.
sometimes i'd like to know something more about a package before i
