Frank Steinmetzger Warp_7 at gmx.de writes:
A tool with perhaps more detail or that parse the ebuild/sources
for even greater detail information?
I was out of country so couldn't read mail the last few days.
My answer to your question: ufed
This program seems very little known around
Jc García jyo.garcia at gmail.com writes:
I use
$ equery u cat/pkg
It list the useflags and what the metadata.xml of the package says
about each of them, plus highlights the active ones if you have the
package already merged.
yea that helps. But the information is a terse, single phrase
On 11/24/2014 01:19 PM, James wrote:
Jc García jyo.garcia at gmail.com writes:
I use
$ equery u cat/pkg
It list the useflags and what the metadata.xml of the package says
about each of them, plus highlights the active ones if you have the
package already merged.
yea that helps. But
When in doubt I just read the ebuild and try to understand what's going on.
A policy would be nice, though, and sometimes even reading the ebuild
leaves me guessing.
As you point out, saying foo: enables libfoo leaves me wandering OK, but
what the f* would I need foo for??
-- Emanuele Rusconi
Emanuele Rusconi emarsk at gmail.com writes:
When in doubt I just read the ebuild and try to understand what's
going on. A policy would be nice, though, and sometimes even reading
the ebuild leaves me guessing. As you point out, saying foo: enables
libfoo leaves me wandering OK, but
5 matches
Mail list logo
