Question for future Debian builds

[IOhannes m zmölnig (Debian/GNU)]

On 2015-12-20 17:53, Giada LoopMachine wrote:
> 
> Hey guys,
> 
> Sorry for the delay! I perfectly understand your pain with JUCE and it's
> (non)packaging status. Actually we are considering shipping "raw" JUCE's
> source code, with no pre-compiled or embedded libraries around. That way
> JUCE would be just a part of the whole source tarball, #include'd and
> compiled by Giada itself when needed. What do you say?

i am not sure i fully understand (having not worked with juce myself).

here's a few things to keep in mind (this might be not relevant at all;
you probably can tell better than me :-))

- we (Debian) prefer to generate *any* generated files during the
build-process, so
- if there are any files that are *generated* (even if they are plain
C++-files), we (Debian) MUST to have the original sources (e.g. an
XML-description used to generate the C++-files), and
- we (Debian) will also need the *generator* executable (that turns the
XML-files into C++-files) within the *Debian archive*.


finally: embedding libraries is generally frowned upon, to eliminate
duplicate work. so as long as giada were the only package using JUCE,
embedding it would probably be OK, but once other applications start
using it as well (a few come to my mind which i would probably like to
package), it definitely should go into a separate package.

fgmawdr
IOhannes