[Development] Policy: supplying the preferred format for modifications for everything we ship

[Olivier Goffart]

On Sunday 29 September 2013 12:56:15 Thiago Macieira wrote:
> >From the Minified javascript thread, I propose this policy:
> The Qt Project will always supply in its own infrastructure the preferred
> sources for modification for whatever we ship. Under the GPL and LGPL, 
> anyone who receives our sources and wishes to redistribute is required to
> do that anyway. Whether the same sources are present in our regular
> tarballs or not, it should be judged on a case-by-case basis.
> 
> For most of our own content, that is easy: we've been doing that since time
> immemorial.
> 
> For any third-party content, we need to have the correct scripts to recreate
> the files.
> 
> Examples:
> 
> Qt binary releases		=> source tarballs
> Qt Documentation		=> source tarballs
> pre-generated lexers and parsers => source files (.g, .l, .y)
> Images					=> original, high-resolution or vector images
> Minified JS scripts		=> original, un-minified scripts
> gnuwin32 binaries		=> gnuwin32 source tarballs

As we do not modify those files, but take them from upstream, having a README 
that say where the file are from is enough.
I don't see why it should be part of the tarball. (and especially they should 
not be in the git repositories)

And most of the JS or images are not under LGPL anyway.

-- 
Olivier

Woboq - Qt services and support - http://woboq.com - http://code.woboq.org