Marc Feeley wrote:
On 14-Jan-09, at 1:04 PM, Per Eckerdal wrote:
(Sorry Christian, I forgot to Cc this mail to the list, so you'll get this mail twice)
Actually I didn't get this second mail of you at all. I've now changed the mailman settings of my subscription to always send me list posts (which should really be the default, imho, but whatever).
My only comment atm is regarding:
If the package resides in a CPAN-like repository, cpan is the package resolver for that repository, and the package name is foobar, you might write (use (cpan foobar /foofoo/bar)) to use the /foofoo/bar module in that package.
A problem I see with this approach is if you move a module from one package to another. All users of that module will then have to adapt their dependency.
(I have to think about this more to see how bad it fares compared with other approaches. Anyway, the Perl CPAN does not do as you describe, but instead index every module, and then when you want to install one, it finds out to which package it currently belongs.)
You also still have a problem with package name conflicts. Maybe you think that's better because you'll only have to make package names "long and ugly". But you pay with the price of tieing modules to packages.
Christian.