I'll object simply by saying that sometimes things can't be fully automated. I don't think that the OSCAR RPM should be created in this manner.
Jason On Tue, 2003-11-04 at 13:28, Benoit des Ligneris wrote: > Hello, > > Yep. This is a solution but it is not a long term solution : I would > like the dependencies to be automatically computed from the oscar > tarball so that we can automate the whole process. > > I think that a solution is to add some "provides" to the OSCAR package > and check that the perl include that we use in OSCAR are well provided > by an RPM package. > > If it is not exported by a given package, we should include the file and > not the perl module. For instance instead of > Initrd::Generic, we should include /usr/lib/systemconfig/Initrd/Generic.pm > > That will allow the dependencies to be successfully computed : the > dependency on the file /usr/lib/systemconfig/Initrd/Generic.pm will be > correct whereas perl(Initrd::Generic) is not correct. > > Ben > * Jason Brechin <[EMAIL PROTECTED]> [03-11-04 10:53]: > > There's always 'AutoReq: 0', which should turn off the automatic > > requirement finding code. > > > > Jason > > > > On Mon, 2003-11-03 at 23:11, Benoit des Ligneris wrote: > > > Hello, > > > > > > While we were doing an OSCAR distro, we (naively!!) > > > , tried to do an OSCAR RPM. > > > > > > While the file distribution causes no particular problem, we have > > > trouble with PERL. OSCAR uses a lot of PERL modules that are not > > > provided by any RPM package and this causes dependency problems : > > > PERL(SIS::DB) > > > perl(OSCAR::AddNode) > > > perl(OSCAR::Configbox) > > > perl(OSCAR::Configurator) > > > perl(OSCAR::Database) > > > perl(OSCAR::DelNode) > > > perl(OSCAR::Distro) > > > perl(OSCAR::Help) > > > perl(OSCAR::Logger) > > > perl(OSCAR::MAC) > > > perl(OSCAR::Network) > > > perl(OSCAR::Package) > > > perl(OSCAR::PackageBest) > > > perl(OSCAR::PackageInUn) > > > perl(OSCAR::Tk) > > > ... > > > > > > This problem is similar to the kernel_picker one I mentionned yesterday. > > > > > > I think that the solution is to replace every SIS::DB instances in all OSCAR > > > perl scripts with a file inclusion but I'm not sure that this is the way to go. > > > Any hints from more experiences RPM experts : > > > Is there a better way to remove those "false dependencies" from the > > > OSCAR RPM ? > > > > > > In fact, we specify explicitely most of the dependencies in the SPEC > > > file (RPM name) and if we force the installation, the package is > > > functionnal however, this is not best practices at all ! > > > > > > Francis founded a way to disable the generated dependency : > > > http://lists.freshrpms.net/pipermail/rpm-list/2003-May/004450.html > > > but it is definetely not the way to go. > > > > > > On another level, our RPM is mandrake 9.2 specific in the sense that some > > > dependencies that we explicitely specified are Distro dependant. > > > What is the best way to achieve cross-distro RPM compatibility ? > > > > > > Ben ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
