Panu Matilainen wrote:
> On Mon, 9 Jul 2007, Mark Hatle wrote:
>
>> You are forgetting that you can query per file dependencies in modern
>> RPM produced packages. If you prune self-provided dependencies you lose
>> this information.
>>
>> --filerequires and --fileprovides. Invaluable in my expe
On Mon, 9 Jul 2007, Mark Hatle wrote:
You are forgetting that you can query per file dependencies in modern
RPM produced packages. If you prune self-provided dependencies you lose
this information.
--filerequires and --fileprovides. Invaluable in my experience.
Heh, I'd never noticed rpm *h
You are forgetting that you can query per file dependencies in modern
RPM produced packages. If you prune self-provided dependencies you lose
this information.
--filerequires and --fileprovides. Invaluable in my experience.
There just is no reason to prune self-fulfilled dependencies.
--Mark
On Fri, 6 Jul 2007, Florian Festi wrote:
Panu Matilainen wrote:
On Mon, 2 Jul 2007, Ville Skyttä wrote:
As for how many dependencies this would eliminate, running some quick
queries
[0] against the Fedora primary sqlite metadata database told me it'd be
about
7.3% of all dependencies (9246/
Panu Matilainen wrote:
On Mon, 2 Jul 2007, Ville Skyttä wrote:
As for how many dependencies this would eliminate, running some quick
queries
[0] against the Fedora primary sqlite metadata database told me it'd
be about
7.3% of all dependencies (9246/126066). This is inaccurate (no
versions
On Mon, 2 Jul 2007, Ville Skyttä wrote:
As for how many dependencies this would eliminate, running some quick queries
[0] against the Fedora primary sqlite metadata database told me it'd be about
7.3% of all dependencies (9246/126066). This is inaccurate (no versions in
dependencies taken into
On Mon, 2 Jul 2007, Ville Skyttä wrote:
Hello,
Is there a good reason why packages "export" dependencies on things that they
Provide/satisfy themselves? For example, if a package ships/provides
perl(Foo) and has some other things that also cause a dependency on
perl(Foo), wouldn't it be a good
On Monday 02 July 2007, Adam Jackson wrote:
> On Mon, 2007-07-02 at 21:50 +0300, Ville Skyttä wrote:
> > As for how many dependencies this would eliminate, running some quick
> > queries [0] against the Fedora primary sqlite metadata database told me
> > it'd be about 7.3% of all dependencies (9246
Ville Skyttä ([EMAIL PROTECTED]) said:
> Worth it? Did I miss something?
Notably, this fixes cases where an app has its own copy of a particular library
set (with RPATH) and still ends up pulling in other implementations of that
ABI. Such as the mozilla/firefox stack.
Bill
_
On Mon, 2007-07-02 at 21:50 +0300, Ville Skyttä wrote:
> As for how many dependencies this would eliminate, running some quick queries
> [0] against the Fedora primary sqlite metadata database told me it'd be about
> 7.3% of all dependencies (9246/126066). This is inaccurate (no versions in
>
Hello,
Is there a good reason why packages "export" dependencies on things that they
Provide/satisfy themselves? For example, if a package ships/provides
perl(Foo) and has some other things that also cause a dependency on
perl(Foo), wouldn't it be a good idea to just prune the dependency at bu
11 matches
Mail list logo
