jfm said: : : There is, if I'm not mistaken, a problem of correct deps : for a multi-perl fink installation. : Recall that some pm's (roughly, those installing a bundle) : must have "Type: Perl x.y.z" in their info file, and be built : with perlx.y.z, to be usable with perlx.y.z _ and those packages : get a name like foo-pmxyz. : If other, non-versioned, pm's have to Depend on those, one : needs an additional package foo-pm (Type: bundle), so the : dependency can get listed as just on foo-pm. : : The problem is how to express correctly the dependency of : foo-pm on the different foo-pmxyz's: the effect should be that : foo-pm being installed is a certificate, for whatever perlx.y.z is : running, that the corresponding foo-pmxyz is there (and not just : some foo-pmx'y'z').
I'm not sure I understand, so this paragraph could be irrelevant, but... That sounds like it would mean that every perl I have would have the same modules installed. That might be nice in that no matter which perl I used, I'd have everything present, but that's not always desireable. For large slow-building ones that I only need to use (vs. develop against) and with a simple dependency tree, all I need is *some* version that has it (that's the whole point of unversioned -pm deps). And it's not even always possible (may not work with an old perl, etc.). More importantly, this would mean that building a new perl on one's machine would somehow have to force building of all the -pm that are already existing for other versions for the new one. This brings up a recent annoyance of mine, though (and it may be a simple rephrasing of the original or else somewhat related or else not at all). The current system seems to require multiple versions of a package to satisfy underlying dependency differences. Consider a package for pure-perl program (that can run under any perl) foo that needs a compiled perl module bar.pm. I really want to have foo: Depends: bar-pm I don't care which perl, so I don't care whether I get bar-pm561 or bar-pm580. But because I could have both perl561 and perl580 concurrently, and bar-pm merely requires "some present perl version" to have bar.pm I need to have foo.info fix #!perl to to point to a perl executable version for which the module is there. Thus I would foo-perl561: Depends: bar-pm561 foo-perl580: Depends: bar-pm580 that install alternatives for bin/foo, and foo: Depends: foo-perl561 | foo-perl580 It feels kinda clunky. And I have to make sure I know whether my depended- on modules are versioned or not (a status which has been known to change, albeit rarely). I'm not sure what if anything can be done, nor even if anything sould be done, but the topic triggered this train of thought:) dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
