RPM Community Forums

Mailing List Message of <rpm-devel>

Re: Filtering automagically generated dependencies

From: Jeff Johnson <n3npq@mac.com>
Date: Fri 05 Oct 2007 - 00:04:33 CEST
Message-Id: <5B4B051A-1BFF-4D16-84ED-750EABE07C9E@mac.com>

On Oct 4, 2007, at 12:56 PM, Mark Hatle wrote:

> Arkadiusz Miskiewicz wrote:
>>> Does the filtering affect the internal per-file dependencies or  
>>> just the
>>> overall package dependencies once they are rolled together?
>>
>> PLD patch applies to overall deps for entire spec. So it's not per- 
>> pkg. It's
>> per-spec. Both per-{pkg,spec} are actually useful but we  
>> implemented per-spec
>> only.
>
> (Without seeing the patch), does this affect the per-file dependency
> generator, or is the filter applied when it's rolled up into the pkg
> dependencies?  I'm concerned about this because (and MV) use the
> per-file dependencies as hints on how to construct partial rpm package
> installs for embedded systems.  If we're not filtering on the file  
> deps,
> then the hints will be invalid, or won't match the packages overall  
> deps.
>

No idea. The whole issue of filtering introduces gazillions of Baroque'n
knobs, bells and whistles in order to use that (imho) cannot possibly be
implemented to everyone's satisfaction. There's more to a package build
tool than Yet Another grep implementation.

But since the only comment -- yours -- is "we anticpate usefulness",
the patch goes in. (Note: there's one patch that maps dependencies
*only* packages as well as filtering dependecies).

Hint: Consider filtering
     Requires: foo > 1.2.3
given an implementation based on macros
    %define _noautoreqdeps libA.so libB.so
patterns. Examine the white space carefully ...

>>> personally I'd like a mechanism to do this kind of filtering on a  
>>> per
>>> package basis... but so far you've talked me out of it.
>>
>> per-spec, too. per-pkg only would require to put filtering 10  
>> times in one
>> spec if it generates 10 pkgs from single spec.
>
> Actually thats what I wanted, was per-spec.  I meant per "source
> package".  Same thing.... :)

You'll be sorry is my prediction. But as long as I can disable
the gunk, and can point the support finger to someone else instead,
I don't really care what patches go into rpmbuild.

73 de Jeff
Received on Fri Oct 5 00:04:44 2007
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.