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 d
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 t
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 uni
emerge --changelog ?
k, sorry :)
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 available, but how do they decide
how they are documented? I'm sorry if i did
Hi!
I'd like to introduce two ideas i had to improve portage.
sometimes i'd like to know something more about a package before i
emerge it.
1. release notes. (for the ebuild, not the application)
as a release notes file exists, a parameter could be used to show the
most recent entry.
maybe