[Catalyst] [RFC] Catalyst::ConfigLoader -- load a config from various formats

[Matthew Lawrence]

Brandon Black wrote:
> On 1/26/06, Perrin Harkins <perrin at elem.com> wrote:
> 
>>On Thu, 2006-01-26 at 18:12 +0000, Matt S Trout wrote:
>>
>>>I don't always have the luxury of being the only person running code on
>>>a given server.
>>
>>There are many ways to do it.  The odds that any two large perl apps
>>will require conflicting versions of a certain module are pretty high,
>>so most people find a way to deal with this if they have multiple apps
>>developed with different frameworks.  Many corporate environments (e.g.
>>Morgan Stanley) develop configuration management systems for handling
>>this.
>>
> 
> 
> Until such a framework ships for the rest of us, as something that all
> perl installations and modules know about, it's not feasible in the
> general case for a large framework being published to the world for
> use on random hosts that don't have such a configuration management
> system.
> 
> It could be fixed by p5p with a rather invasive change to allow
> multiple versions of a module to be installed simultaneously in
> versioned subdirectories, with "use", "require", etc picking up the
> latest available normally, but also allowing "I want exactly version
> X" to work.  And from there it's trivial to use module-building tools
> that use exact dependencies where neccesary instead of "at least X"
> dependencies.  lib/ would get a bit polluted with unneccesary old
> versions over time, but there's not a lot of clean ways to clean those
> up (user scripts in someone's home directory might be the only ones
> left still using old version X of some module).
> 

Ironically enough, Ingy has a module that might help here:

http://search.cpan.org/~ingy/only-0.28/lib/only.pm

See specifically INSTALLING MULTIPLE MODULE VERSIONS.

Matt