See my other comments regarding
path based filtering, all of which is non-portable
even in linux, where paths/needs are on a "de facto" per-interpreter,
per-distro, and per-FHS-version basis.
General rule based filtering on content (i.e. using "man 5 magic" strings), or
a more
general configuration mechanism, needs to be attempted.
I also see little need to expose (as @rpm.org has done) configuration that
hardly anyone changes, and the need for changes is often measured in
years, where a later version of RPM could easily be deployed).
Short answer:
Not the right fix. *shrug*
73 de Jeff
On Aug 26, 2013, at 2:57 PM, Per Øyvind Karlsen wrote:
> This patch will make the dependency generator only generate ruby and python
> dependencies for executable and modules, this way preventing dependencies
> being generated for such as ie. private python files shipped with some
> package at some non-standard location, not meant to be available/exported for
> other use by other software.
>
> --
> Regards,
> Per Øyvind
> <rpm-5.4.7-only-generate-ruby-and-python-deps-for-executables-and-modules.patch>
______________________________________________________________________
RPM Package Manager http://rpm5.org
Developer Communication List rpm-devel@rpm5.org
