Le 22/03/2014 12:37, David Prévot a écrit :
> Le 22/03/2014 05:33, Emilien Klein a écrit :
>> On 03/21/2014 11:22 PM, François-Régis wrote:
>>> Le 21/03/2014 07:45, Emilien Klein a écrit :

>>> We may have something like :
>>> * Origin tarball should not include any minify code.
> Maybe there is a missing “sourceless” here: it’s perfectly fine for a
> source package to embed a convenient binary/prebuilt copy, as long as it
> is not used in the binary package, but instead rebuild it from source
> and ships the rebuilt version. In order not to make minified JavaScript
> any different, the first point should read:
> * Origin tarball should not include any sourceless minified code.

This is exactly not what Marcelo said in [0] and its reference to [1]
shows that he removes minifies files from origin tarball althought they
have source files.



>>>> Regarding the removal of the minified files: that is done to comply
>>>> with the DFSG, as minified files are assimilated to compiled objects,
>>>> not source code. As Debian requires the source to be provided, not the
>>>> compiled binaries, the minified files must be removed fromt the
>>>> upstream tarball.
> Again, only if the source is not provided. An alternative in case
> upstream provides sourceless minified JavaScript in their tarball, would
> be to ship the source (e.g., dug up from their source repository, or
> from JQuery) inside the debian directory, and rebuild it for (or do
> nothing if it isn’t shipped in) the binary package: it can save a repack.

I may be wrong but perhaps providing minified files in source tarball
(which are considered as binary files) is DFSG compliant providing we
have the sources, but debian policy is to exclude them from sources.

> Alternatively, the Excluded-Files feature of uscan(1) can do it for you.

Of course it could.


Attachment: signature.asc
Description: OpenPGP digital signature

Pkg-javascript-devel mailing list

Reply via email to