Jeff Wrote: 
> Rather than a yum repository (that needs to be kept up to date, and can
> get out of date easily, etc), I've learned that FC5 tends to "just
> have" a lot of the stuff that we need.
> 
> Couldn't we just:
> 
> (1) Get rid of the stuff in SlimServer's "local" CPAN directory,
> (2) Get the dependencies "right" in the RPM so other FC5 components (if
> any) are installed automatically, and
> (3) For the PERL CPAN stuff (since this isn't RPM packages), have
> .rpmspec code that verifies the "right stuff" is installed, or install
> using CPAN archives that already exist?
> 
> I'm not sure what was done on Debian.  But I know that I just recently
> installed MythTV, and 99% of the dependencies were already satisfied by
> what FC5 offers "out of the box" ...
> 
> This seems to me that it would be more likely to work with FC6, etc,
> whenever that comes ...

Back in town yesterday... I'm all for #1-3. I'm not sure that a yum
repository would require more maintenance than an RPM... basically it
consists of RPMs and their headers as separate files. The reason I
suggest a Yum repository is for ease of installation.

RPM recognizes dependencies, but Yum autoloads them for RPM. My
Squeezebox had been running on a FC3 server, and if I remember
correctly, I had to package up some other Perl stuff for it (for some
reason, Time::HiRes comes to mind) to get it to work right (this is an
SB1 and it was a long time back). Unless FC5 contains all the packages
needed (and it may), there may need to be more than one RPM (in order
to get rid of all the CPAN stuff in slimserver and use the system
libraries instead) in which case Yum may be preferable.

-al


-- 
Al Pacifico
------------------------------------------------------------------------
Al Pacifico's Profile: http://forums.slimdevices.com/member.php?userid=5640
View this thread: http://forums.slimdevices.com/showthread.php?t=23594

_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/unix

Reply via email to