On Fri, 30 Jan 2004, Chris Adams wrote: > Once upon a time, James Olin Oden <joden@xxxxxxxxxxxxxxxxxxxxx> said: > > > I didn't set any dependencis, rpmbuild seems to find it itself within > > > the %install-macro. How can I change this or how can I disable automatic > > > dependency checking? > > > > > It sure does and you don't want to change this. Your scripts do use these > > perl modules, and so they do depend on them. > > Not always, and that is the problem with perl dependency checking. > There are a number of modules that will look for other modules; if they > are found, more functionality and/or integration is possible, but if > they are not, the first module still does what it says it does. There > is no way for a script to be able to tell this; it _must_ be done by > hand (so I end up disabling auto-dependency generation and list them > manually). > > It would be nice to be able to allow auto-dependency generation, but > exclude certain modules (something like "NoRequires: blah"). > The way I handle this with non-perl packages, is I insert a "fake" provides in the spec file for the thing that rpm will detect as a dependency. cpanflute2 presently supports the --requires option, and it would be real easy to create a patch to support --provides. Well I just did, so if you download the RPM-Specfile from cpan (the 1.13 version) and apply the patch found at: http://lee.k12.nc.us/~joden/misc/patches/provides.patch All you have to do is something like: cpanflute2 --buildall --provides="perl(lib1) = ver1" ... --provides="perl(lib2) = ver2" tarball And your problem will go away, while yet still allowing the "real" dependencies to be tracked. Cheers...james P.S. Chip don't download the patch if you see this, as I need to clean it up. I think its time for pod for cpanflute2 itself (-; _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
