RPM Community Forums

Mailing List Message of <rpm-devel>

Re: Filtering automagically generated dependencies

From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
Date: Fri 05 Oct 2007 - 08:25:28 CEST
Message-Id: <200710050825.28305.arekm@pld-linux.org>
On Friday 05 of October 2007, Jeff Johnson wrote:
> On Oct 4, 2007, at 12:52 PM, Arkadiusz Miskiewicz wrote:
> > Note that -x binary is not a option since it has some other
> > autogenerated deps
> > that we want to have.
>
> Not true. chmod -x is _ALWAYS_ an option, re-add the execute bits
> with %attr.

Not true? AFAIK deps autogenerator ignores binaries that aren't executable. So 
it won't find any deps for binary A and that's what I'm talking about.

Example:
bin/blah generates R: libjbj.so.1, R: libwrum.so.3. You want to filter out 
libwrum.so.3 only.

chmod -x bin/blah is not a option. It will require manual R: libjbj.so.1 in 
spec which sucks.

> >> 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.
>
> Say what? Adding a pattern once in a per-distro filtering file
> somehow becomes 10
> additions for sub-pkgs? Explicit details please ...

There is package A that Requires: libcrap.so.1 and there is package B that 
Requires: libcrap.so.1. Tell me now how to filter out libcrap.so.1 ONLY for 
package A but NOT B with per-distro filtering rule.

> 73 de Jeff

-- 
Arkadiusz Mi¶kiewicz        PLD/Linux Team
arekm / maven.pl            http://ftp.pld-linux.org/
Received on Fri Oct 5 08:25:31 2007
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.