I submitted a package to the tracker that is pure perl (gd-svg-pm), but it depends on a versioned package (gd-pm). The package was not yet moved to unstable because of an apparent problem with the versioning.
I quote the comments on the tracker (from Dan Macks):
"One could have gd-svg-pm installed, and gd-pm installed with its dependencies satisfied by gd-pm581. But now gd-svg-pm *only* works under perl 5.8.1 (since there's no gd-pmXXX for other perls). (*)
So you'll need to have a family of packages gd-svg-pm581 and friends, each depending on the analogous gd-pmXXX. But that's gonna suck because each will conflict with the others.
I don't know the ideal solution here. Maybe have the meat of this module in gd-svg-pm but split off gd-svg-pmXXX each that depends on the main package and also the relevant gd-pmXXX (but doesn't actually contain anything).Then one would install gd-svg-pmXXX for whichever perl one wants."
(*) there is actually gd-pm for 560, 580 and 581, so I am not sure what Dan meant here.
As I understand this was briefly discussed on #fink, but since it affects a fair amount of fink packages,
I think it should be posted here as well. My questions are:
1. what do others think would be the best approach to handle this situation
2. is this the first time this has been an issue? I haven't checked, but I asssume there are more pure perl packages that depend on versioned perl packages.
3. until an official solution has been accepted, can the package gd-svg-pm (and bioperl-pm ;) be move to unstable?
thanks,
- Koen.
------------------------------------------------------- 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
