On Thu, Jun 14, 2012 at 6:37 PM, Jonas Smedegaard <[email protected]> wrote: > On 12-06-14 at 05:40pm, Pau Garcia i Quiles wrote: >> We should just treat JavaScript libraries exactly the same way we >> treat C/C++ libraries, with soversions and all. That makes multiple >> runtime versions co-installable and co-dependable, which would solve >> the problem. > > How to resolve the SO-name for JavaScript?
By full path. I. e. instead of: /usr/share/javascript/jquery/jquery.js let's have: /usr/share/javascript/jquery/1.7.2/jquery.js Which is actually the same thing the Google CDN does: https://ajax.googleapis.com/ajax/libs/jquery/1.7.2/jquery.min.js Then the package would be libjs-jquery56 instead of just libjs-jquery, as we do for C/C++ libraries. At the beginning we would need to maintain sonames ourselves but with time, I'm sure we will be able to teach upstream about sonames, even better. I've done that for 2 C++ libraries (libmsn and Wt) in the past few years and it's been working fine for a long time already. -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) _______________________________________________ Pkg-javascript-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
