Ok, I have to admit the subject may be a bit confusing, so let me get
the motivation first:
Often people want to know the dependencies of a package. Not much of a
problem when they know how to use auxget or the portageq metadata
commands. However these all work on the specific DEPEND, RDEPEND and
Other than a text editor?
I'd like to have a tool that can add USE flags on a per package or
global level. (I'm doing this in some build scripts and would prefer
just to have a tool, rather than sed or some other shell hackery).
I couldn't find anything via a quick search on google.
Here's my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Mauch wrote:
So now I was wondering a) if I'm the only one who finds this
feature useful and b) if adding it at the dbapi level (in dbapi.aux_get)
would be considered a good idea, so it could be used by other tools?
I think of aux_get as a
It would be useful if ebuilds listed any USE flags that don't affect the
package the ebuild is for, so that emerge knows it doesn't need to rebuild
the package if these change (or are newly added to the ebuild). These
include flags like glibc-compat20 and nptl on glibc-2.4-r3 (if they
aren't
m h wrote:
Other than a text editor?
I'd like to have a tool that can add USE flags on a per package or
global level. (I'm doing this in some build scripts and would prefer
just to have a tool, rather than sed or some other shell hackery).
I couldn't find anything via a quick search on
Well, you just described what flagedit does, only with a bit
tidier interface ;).
In general, I'd suggest taking a look under app-portage category..
George
четвер, 26. жовтень 2006 20:08, m h Ви написали:
[...]
Here's my interface:
use-config --add --component sys-devel/gcc --flag fortran
