[Kdenlive-devel] Kdenlive packaging policies

[Jean-Michel Pouré]

On Mon, 2008-12-15 at 10:36 +0100, Mads Bondo Dydensborg wrote:
> The greatest obstacle to me is getting all the .spec and .deb files
> right. 
> They more or less need to differ for each distribution, and for many
> also 
> needs to include dependencies outside the std. repos.

A few years ago, I took part in pgadmin projects. We build daily RPMs
everyday from SVN and user just loved it. These are static build, with
very few, let us say NO dependency.

Packaging is really the KEY point in the next release. If you don't
provide de working solution, bug fixes to users, they turn away and
write very bad appraisals on Internet. This spreads and ends-up in a bad
situation.

If you consider Kdenlive from the developer point of view, then yes it
is easy to compile. But most Linux users today are non-technical folks
and they don't know how to compile. For example, most of my friends now
use GNU/Linux and none of them know how to compile.

@dan: do you think it is possible to build MLT staticly, with no
dependency to ffmpeg, libavformat and libavcodec being included in MLT
during static compilation. I know this means compiling ffmpeg staticly
against various libraries. What is your technical opinion?

Kind regards,
Jean-Michel