Hi Pau.

2012/5/1 Pau Garcia i Quiles <pgqui...@elpauer.org>:
> Hi,
> I'm the maintainer of Wt (  http://packages.debian.org/sid/witty  ).
> Since version 3.1.11, Wt uses jPlayer to implement the WVideo and
> WAudio classes. Today I discovered SwfTools provides an AS3 compiler
> (previously I though only Flex would work, which was a problem because
> Flex is not available on Debian.
> Now I am considering packaging jPlayer, which is itself a jQuery
> plugin. A few questions:
> - Is there a "Debian Guidelines for JavaScript packagers" document?

We have a Debian JavaScript Maintainers wiki page [0] and in
particular a Debian JavaScript Policy  page [1]. The latter specifies
package naming, although not specifically for jQuery plugins.

> - Many jQuery plugins have been combined into the jquery-goodies,
> although the have different upstreams. Should I add jPlayer to the
> jquery-goodies package or package it on itself (it has a JavaScript
> part and a Flash part) ? (I'd rather go for the latter unless policy
> is the former)

Having recently uploaded a new jQuery plugin [2], I would suggest you
package it on itself. The fact that there is a Flash part next to the
js past seems to also be a good reason to package this separately and
not in jquery-goodies.

To summarize, this is my suggestion:
- Make a separate package
- Name the source package jquery-jplayer
- Name the binary package libjs-jquery-jplayer
- Install the scripts in /usr/share/javascript/jquery-jplayer

To the other members of the JS packaging team: let us know if you
disagree with this naming scheme. If not, we could (as suggested
before) update the Policy page with information on how to name jQuery

Pau, have you considered joining the JS packaging team [3]? And
subscribing to our mailinglist? [4]


[0] http://wiki.debian.org/Javascript
[1] http://wiki.debian.org/Javascript/Policy
[2] http://packages.qa.debian.org/j/jquery-lazyload.html
[4] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Pkg-javascript-devel mailing list

Reply via email to