On Tue, 26 Jan 2010, Till Maas wrote:
> On Tue, Jan 26, 2010 at 12:13:33PM +0200, Panu Matilainen wrote:
>
>> %global _use_internal_dependency_generator 0
>>
>> The external dependency generator doesn't create the file "coloring" that
>> the multilib magic needs to operate. So you'll get conflicts on all paths
>> where content differs.
>
> How can one both get the file "coloring" and add own dependencies with a
> script to an rpm? Iirc the internal dependency generator needs to be
> disabled to be able to specify a special script to add dependencies.
The sorry state of things right now is that there's no generic way that
works in every situation with the internal dependency generator, but for
some cases its possible:
1) All the require/provide helper scripts the internal dep generator uses
can be overridden and customized, such as the __perl_provides/requires
scripts.
2) Custom requires etc can be added in a scripted manner with
Requires: %(some-custom-script)
but this is rather limited as the script would run at early spec
parsing state, where one typically wants to generate dependencies from
what was just compiled. Which is possible (but cumbersome) for the
things that use helper scriptlets, ie case 1)
FWIW, I'm working on it. The internal dependency generator is a serious
bottleneck to what packagers would want/need to do, and the pile of ugly
hacks in it is getting a bit much.
The first step is probably to move all the actual dependency generation
work out of librpmbuild into helpers that can be overridden and
customized, so that 1) becomes a general (even if cumbersome) solution.
The main offender is elf dependency extraction which needs to be lifted
into separate helper, which should also open new possibilities for dealing
with non-native elf files (ie cross-builds).
It needs a whole lot more than that of course but you gotta start
somewhere...
- Panu -
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
