On Sun, Oct 23, 2011 at 5:29 PM, Paul Wise <p...@debian.org> wrote: > On Sun, Oct 23, 2011 at 11:13 PM, Raphael Hertzog wrote: > > > And with javascript libraries, there's no failure at build time, > > you only discover much later when something is not working... > > This is the crux of the issue and it is not specific to JavaScript > libraries, anything that is interpreted has this issue. I'm pretty > sure I've seen API breakage in libraries implemented in Python for > example. > > I agree.
So far it seems I have been pretty lucky with my package witty, which depends on jquery but upstream is not really happy Debian and Ubuntu replace the jquery version they have tested with. > What are your thoughts on this topic? One of the other problems with embedded JavaScript libraries is that > often only the pre-compiled/obfuscated/minified version is > distributed, which would be a violation of DFSG item 2. > > IMHO that should not be a problem provided that: - The JavaScript library is open source with the proper license, etc - Upstream is using the Javascript library "as is" (i. e. with no local modifications) Maybe README.Debian should mention "this package embeds the JavaScript library XXX which is available independently in package libjs-XXX (source package: libjs-XXX) :-? -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer)
