openshot.developers team mailing list archive

[Jonathan Thomas <Jonathan.Oomph@xxxxxxxxx>]

Thanks for the suggestion Tony.  I'm no expert on packaging
applications, and I'm learning every day.  That being said, here are my
thoughts.

The MLT project has configure scripts and make files for the python
bindings (it uses Swig).  OpenShot cannot create those files... it's
done via the MLT build process.

OpenShot really doesn't need much configuring... it just needs Python,
GTK, and PyGooCanvas.  The rest of our dependencies have their own
source code tarballs, and their own unique build processes.  Hope this
helps.

-- 
Include swig files in the tarball/repository
https://bugs.launchpad.net/bugs/443202
You received this bug notification because you are a member of OpenShot
Developers, which is subscribed to OpenShot Video Editor.

Status in OpenShot Video Editor: New

Bug description:
The whole point of having tarballed releases and a public repository is to allow people to build the software by themselves (in any architecture and distribution) and contribute. It's quite easy to compile ffmpeg and mlt by hand and run openshot with personal versions, but the python-mlt dependency is an openshot creation and therefore the files for its creation should be included in the tarball/repository.

Ideally, the tarball/repository should include a configure script that would detect that the correct version of mlt is installed, detect that swig is installed and generate the wrappers automatically.

Furthermore, this is necessary to "GPLize" OpenShot a little bit more, since python-mlt can be considered a compiled library whose source code is not being made available.