[Openstack-devel] Websockify has been rejected from upload in Debian

[Joel Martin]

Thomas,

On Wed, Apr 10, 2013 at 10:54 AM, Thomas Goirand <thomas at goirand.fr> wrote:
>
> Well, why don't you just create the .swf file in your build process, and
> remote the file completely? That would satisfy everyone. I, too, would
> like to have a system which would work with every browsers!!!


No, that would be a big hassle for me and for everyone who clones and
integrates the master noVNC repository. Building the swf file from source
is possible but it is temperamental and uses tools that are not part of
standard distros (e.g. flex).


> - You could maintain your own downstream repo of noVNC that doesn't
>  > contain the binary pieces and merge changes into it.
>
> Well, why don't you try to simply have a realy, open source and free,
> software? Don't you have the source code for the .swf file? Where does
> it come from?
>

noVNC is already open source and free software; it fulfills all four
fundamental freedoms of free software (
http://www.gnu.org/philosophy/free-sw.html). It may not match the stricter
requirements that Debian requires, but it is still 100% FOSS. All the
source necessary to use and modify noVNC is available. Lots of other
projects include generated files in their trees (configure, Makefile, PNGs,
JPGs, etc, etc) and Debian has no problem with those. And just like those
files, the swf file can be recreated. If you need me to create a git
submodule link to the sources necessary to build the swf, I am fine with
that.

If none of the solutions I suggested is acceptable, then please suggest a
solution that does not involve making life harder for every other user and
integrator of noVNC by forcing them to go through an arcane build process
to build something that they are VERY unlikely to care to modify anyways
(but like I said, if they care to they can modify and build it).

Regards,

Joel Martin (kanaka)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/openstack-devel/attachments/20130410/ca3f67e4/attachment.html>