[Pkg-javascript-devel] Javascript library versioning

[Andres Rodriguez]

Dear All,

Over Ubuntu we have been considering the upgrade of a couple Javascript
packages, differing from Debian versions. Specifically, we are considering
upgrading YUI to 3.5. Currently, both in Debian and Ubuntu we are shipping
YUI 2.8.2r1.

While considering the upgrade, I was raised the concern that in the current
packages we are not including any major version number of the library,
which means that we cannot ship different version of it in parallel.

Usually, between major releases, changes in the code are needed, and
sometimes, it is necessary to ship different versions of it. However, in
the current approach, and according to policy, we would be unable to ship
different version of the library because of the installation paths
(/usr/share/javascript/<library>/*.js).

So, in order to not differ with Debian, we were wondering a few things:

1. Would it make sense to include versions in the installation paths? (i.e.
/usr/share/javascript/yui/2.8.2/*.js , /usr/share/javascript/yui/3.5.1/*.js)

2. According to the YUI loader, the root path to be prep-ended to the combo
service is "<version>/build". For this reason, it also makes sense for us
to be using versioned installation paths.

All of the above would mean a few things:

1. Adjusting current package to contain major versions (at least in the
binary package)
2. Upload a new source package for any major version (i.e. 3.5.X)

Given that we don't want to differ from Debian, and try to stick with the
policy, we were wondering what are your thoughts about this?

Thank you in advance.

Look forward to hearing from you.
-- 
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
Systems Engineer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/attachments/20120614/a7de013f/attachment.html>