On Oct 15, 2007, at 6:38 PM, Michael Jennings wrote:

> On Thursday, 04 October 2007, at 10:59:22 (-0400),
> Jeff Johnson wrote:
>
>>  Right next to the mechanism for filtering internally generated  
>> soname
>>  dependencies in the PLD patch, is a means to map all dependencies  
>> back
>>  to package NEVRA.
>>
>>  The rationale for the mapping (as far as I understand) is to  
>> simplify
>>  finding the name of the object that contains the provides that  
>> satisfies
>>  a require.
>>
>>  WIthout getting into semantic usage cases (e.g. whether soname and
>>  file dependencies are a good or a bad idea), I ask
>>
>>      Should the mechanism be added to HEAD?
>
> If the mechanism is clean and completely dynamic (i.e., no external
> maintenance required and done automatically at build time), I'd sure
> like to see it.
>

All depends on the relation between the build <-> install machines.
If the build system has content that is sufficiently close to the  
install system,
then the computation of the package that provides a dependency is just
a lookup.

The lookup is clean, completely dynamic, done automatically, and  
completely
obscure. Will work fine for building in chroot's like PLD, but will  
have the usual
problems of lack of precision using the open-ended versionless
     Requires: foo

The private reason for adding (with default disabled) is to hand zealots
a completely implemented package-only mechanism, rather than discussing
the relative worth of soname, file, name space, interpreter,  
parentdir, linkto etc etc
animules in the rpm dependency menagerie.

I believe in lobotomies as a cure for stoopidity ;-)

73 de Jeff