Daniel Macks <[EMAIL PROTECTED]> wrote: > On Mon, Jan 12, 2004 at 08:39:20PM -0500, David R. Morrison wrote: [snip]
> > This would work pretty well, I think. However, there is another aspect > > to the problem. Some pm packages install binaries in /sw/bin and/or > > man pages in /sw/share/man. If you have different pmXXX packages, they > > will want to install the same file. > > Good point. > > It sounds like it's a given that the set of /sw/bin files is the same > for each XXX (from a human or other public interface perspective; > would obviously differ in #!/sw/bin/perlXXX). I can't think of a > situation where one would need those files from more than one perl > version installed at one time. > > > One short-term solution to this is to allow foo-pmXXX to replace foo-pmYYY > > for all the other YYYs. > > That means one could never have more than one perl have a given module > at a time. Not true. The most common way in fink that "replaces" is used is to have one package both conflict with and replace another package. However, if I simply put "Replaces: bar" into foo.info (wihtout using Conflicts), then when you install foo.info, dpkg will overwrite any files of the same name which belong to bar. I did this with a few of the pmXXX packages this morning: foo-pm560.info got "Replaces: foo-pm581" whereas foo-pm581.info got "Replaces: foo-pm560". This way, the binary files correspond to the most recently installed version of the package. -- Dave ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
