----- Original Message ----- > From: "Fred Gleason" <[email protected]>
> On Mar 3, 2013, at 11:10 53, Jay Ashworth wrote: > > > They test, and if necessary, fix, your set of installed dependencies, > > since the packager who sets them up should know what that is by the > > time he or she would be ready to create a package. They're sort of a > > build-from-source version of interpackage dependencies. IIRC, RT predates > > repo-based packaging. > > Ok, I'm just a bit slow I guess. "Testing" a dependency I get -- "do > we have it?, is it the correct version?" (although methinks that this > is the proper domain of the configure script). But "fixing" -- what > exactly is this target expected to do? Is this something like Gentoo > e-merge -- go fetch all the sources automatically and build them? Well, the situation is, admittedly a bit different; RT is a perl app, so yes, what it does is to go CPAN in the tops of the trees of everything which it has on it's prereq list, trusting CPAN to pull in all the subsidiary dependencies. Since CPAN is effectively distro independent, this works. In the case of Rivendell, the way you would do this -- and the packages you'd need to get -- would be distro specific, and a relatively defensible argument could be made that once you'd gone that far, you should go the last 20% and do the build, making the package and tagging it with the proper dependencies. So, I guess, "never mind". </litella> Cheers, -- jra -- Jay R. Ashworth Baylink [email protected] Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274 _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
