On Tue, 14 Dec 2004, Matthew Miller wrote: > On Tue, Dec 14, 2004 at 01:42:58PM -0200, Rodolfo M. Raya wrote: > > It is not rpm itself what demands a certain Perl module. It is the > > package that you want to install what requires a Perl module. Instead of > > complaining at the way rpm works, complain to the guy that packaged that > > thing you want to install. He is the one that chose to require Perl > > installed via rpm. IMHO, you are barking at the wrong tree. > > Except, don't complain to that person, because that's the normal and proper > thing to do. i'm not going to get into a religious discussion here, but i just want to summarize what i've been going through trying to install a simple rpm. and it may very well be that i'm making this *way* more difficult than it has to be. and, if i am, please, someone put me out of my misery (by *explaining* the correct strategy :-). i want to install the "kwiki" package, and there's a pre-built rpm version at the dag.wieers.com repo: http://dag.wieers.com/packages/perl-Kwiki/ so i add dag's repo URL to my yum configuration and run: # yum install perl-Kwiki ... snip ... Error: missing dep: perl(Template) for pkg perl-Spoon Error: missing dep: perl(IO::String) for pkg perl-IO-All ok, so i obviously need a couple more rpms, and neither of these appear to be in the dag repo (at least, yum doesn't find them there and, based on previous discussion here, i need to get them and install them.) so, off to find and install "cpan2rpm". no problem, that's easy enough. and then: # cpan2rpm IO::String seems to work fine, use "rpm" to install. one down, one to go. hey, maybe this won't be so bad (even though it's *still* more of a pain than it should be). next: # cpan2rpm Template ... snip ... Unable to build module, the following dependencies have failed: AppConfig >= 1.55 ok, fine, take a chance and try: # yum install perl-AppConfig hey, found it and installed it! onward. back to trying to "cpan2rpm Template", now that we've popped "AppConfig" off the stack: # cpan2rpm Template deliberately choose to leave out some (allegedly components), and it builds. so, try a "--test" install to get: # rpm -ivh --test perl-Template-Toolkit-2.14-1.i386.rpm error: Failed dependencies: perl(GD) is needed by perl-Template-Toolkit-2.14-1.i386 perl(GD::Graph::area) is needed by ... lots of GD-related stuff snipped ... perl(Pod::POM) is needed by perl-Template-Toolkit-2.14-1.i386 perl(Text::Autoformat) is needed by perl-Template-Toolkit-2.14-1.i386 perl(XML::RSS) is needed by perl-Template-Toolkit-2.14-1.i386 perl(XML::Simple) is needed by perl-Template-Toolkit-2.14-1.i386 perl(XML::XPath) is needed by perl-Template-Toolkit-2.14-1.i386 ok, at this point, i have to guess that this is just *not* the proper way to be doing this. it appears (and i could be completely wrong) that the need to satisfy dependencies via "cpan2rpm" is making a mess of "yum" being able to list all of the dependencies for a single rpm file. in short, until you use "cpan2rpm" to build the rpm file, yum can't possibly make a list of its dependencies. thoughts? am i just misunderstanding something trivial but crucial? should i take this to the yum mailing list? rday _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
