On Fri, Jan 29, 2010 at 12:07:35AM +0200, Panu Matilainen wrote: > 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. > 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. Is it maybe easily possible to just add another dummy helper script, that by default does not create any Requires/Provides, but is called for every RPM, e.g. __extra_provides/requires. Then this could be overwritten without disturbing the other dependency generation steps. Regards Till
Attachment:
pgp2qeDbyeVyA.pgp
Description: PGP signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
