On Mon, 22 Aug 2005, Graham Murray wrote:
> However it should be possible to know all of files that the package
> may install.
You would have to write a utility that looked at ALL the possible USE
flags a package could make use of and build a tree that was stored in a
database (not to mention, yo
Nick Rout <[EMAIL PROTECTED]> writes:
> neither equery nor any other program can predict what will be installed
> in a package, because that varies with architecture and USE flags.
>
> So there is no direct equivalent.
However it should be possible to know all of files that the package
may instal
Nick Rout schreef:
> neither equery nor any other program can predict what will be installed
> in a package, because that varies with architecture and USE flags.
>
> So there is no direct equivalent.
You're right; I forgot that equery and its equivalents work by default
on installed packages (alt
neither equery nor any other program can predict what will be installed
in a package, because that varies with architecture and USE flags.
So there is no direct equivalent.
You either have to work it out for yuorself, ggogle or ask here.
This topic has been covered many times on this list.
If
I tried it and it didnt work - though the package I tried it on was a
masked one.
On Sun, 2005-08-21 at 21:26 -0500, Harry Putnam wrote:
> Holly Bostick <[EMAIL PROTECTED]> writes:
>
...
> One piece of man page may indicate otherwise:
>
>list pkgspec
> This command lists
Holly Bostick <[EMAIL PROTECTED]> writes:
> Rennie deGraaf schreef:
>> What command does one use to find what package(s) provide a particular
>> file, given that that particular file is not present on my system? For
>> example, I need a program called "foobar", but don't know what package
>> provi
6 matches
Mail list logo
