Graham TerMarsch wrote:

> Only thing to watch out for, though, is that many of the JS libraries come 
> with their own bundled copy of "Prototype" (http://www.prototypejs.org/), and 
> the provided version varies depending on when those JS libraries were 
> released.  With the current versions of these Alien packages on CPAN, 
> the "Alien::scriptaculous" package has the most recent version; if you're 
> installing files from multiple packages, do this one last. :)
> 
> I'd considered the idea of setting up a separate "Alien::prototype" package 
> to 
> contain the latest version of Prototype and then have everything else depend 
> on that instead, but haven't yet had a chance to fully think about how to 
> handle things like version conflicts or dependencies on old copies of 
> Prototype.  So, for now at least, each of these Alien:: packages 
> comes "standalone" and has no requirements on any other Alien:: package.

I'd definitely go with having a separate Alien::prototype. I know that the whole
extended prototype family likes to bundle the version they work with together
with the library, but this can probably be handled by using versions of the
Alien:: packages. I'd even probably try and match the Perl version with the JS
version.

Then Alien::Prototype::Window can depend on one version of Alient::prototype and
Alien::scriptaculous can depend on another.

-- 
Michael Peters
Developer
Plus Three, LP


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/[email protected]/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to