[Pkg-javascript-devel] Policy on installation of source and compiled (minified) versions of a library (was: Request to Join Project Debian JavaScript Maintainers from François-Régis Vuillemin (frv-guest))

[Ben Finney]

Jonas Smedegaard <dr at jones.dk> writes:

> Quoting François-Régis (2014-03-06 22:59:20)
> > what is the preferred way :
> > - install a minify version an keep the orginal in source package
> > - install both minify and original source
> > - just install original source
>
> Install both. Some users may serve the minified version as-is, while
> some other users may want to join multiple files where better
> minification may be gained from joining source files instead of
> pre-minified files.

Other languages – e.g. Python, Ruby, Emacs's elisp, etc. – have a policy
on what packages should install and where they should install them.

The establishment of such a policy has enabled conventions for packaging
tools (e.g. ‘dh_python’) to perform the compilation and renaming in a
standard manner for all packages using the tool.

What is the Debian ECMAScript (JavaScript) policy on:

* Whether to install source and/or compiled (minified) versions?

* What compiler (minifier) to use by default?

* Where to put the source and compiled versions during install?

* How to name the installed files so that library names and versions can
  predictably be located?

etc.

If such questions aren't yet answered in a Debian-wide policy, what are
the current consensus on these? What prospect is there to have the
discussions needed to reach a consensus for policy?

-- 
 \       “When a well-packaged web of lies has been sold to the masses |
  `\    over generations, the truth will seem utterly preposterous and |
_o__)                    its speaker a raving lunatic.” —Dresden James |
Ben Finney