[Pkg-javascript-devel] JavaScript policy?

[François-Régis]

Hi Ben,

Le 31/03/2014 00:03, Ben Finney a écrit :
> François-Régis <frv at miradou.com> writes:
>> As initiator of the thread, I may recall that the question we ask is
>> "Should we remove from source tarball minified versions of source
>> files existing in tarball".
> An outcome of the thread is to show that the original question is
> ill-posed, because it hides some important assumptions. Those
> assumptions are now evident, and important questions come from them:

Thank you for the ill-posed, if you've read the thread, you can see that
my first proposal was to remove any minified file from any original tarball.

This does'nt meet a consensus.

> * How do we know – and demonstrate to anyone who asks – the truth of the
>   assertion that the source is actually the corresponding source of the
>   exact non-source file?

Before asking how do we know, we should ask do we need to know (and this
in fact the question of the thread).

To extend this, we provide lots of picture files and good practice is to
have a so called source file (xcf, svg or whatever) but noboby can
guarantee that the bitmap file (png, tiff, jpeg ...) is actually sourced
by coresponding source file. Do we have to remove them from arig tarball ?

>   My answer to this is: Currently, we don't know that at all. We take
>   upstream's word for it, though upstream frequently has no incentive to
>   guarantee that to us and can easily make mistakes in ensuring it.

You're right so we take care to which is pristine upstream and which is
provided in binary package. And people using debian source packages
outside debian should take care of it, but can check that upsream
tarball is the same as debian tarball.

> * How do we maximise the certainty that what we ship in the source
>   package has no files without corresponding source?
> 
>   My answer to this is: 100% certainty can be achieved by automatically
>   omitting the non-source files from the Debian source package.

Once again you maximize one thing but this could minify other things,
like having a pristine upstream tarball. This is the debate.

> * How do we maximise the certainty that what we ship in *every future
>   version* of the source package has no files without corresponding
>   source?
> 
>   My answer to this is: Again, 100% certainty can be achieved by
>   automatically omitting the non-source files every time from every
>   Debian release of the source package.

I don't see any difference from you previous arguments.

> * The Debian Social Contract obliges us to provide corresponding source
>   for every file in Debian. Should we rate the promise so unimportant
>   that we risk shipping a file without corresponding source?
> 
>   My answer to this is: No, we should do what we can to meet that
>   obligation, and guarantee it to our recipients in a manner that they
>   can independently verify.

The question here is to accept minified versions of files that have
sources in orig tarball,

> Whatever your answers to these questions are, I hope you can understand
> that they are necessary to provide context to the question you would
> like answered.

I just try to have responses to the question I've adressed "Should we
remove from source tarball minified versions of source files existing in
tarball". The response may depends on context but please deatails which
kind of contest.

Cheers,

-- 
François-Régis