Message: previous - next
Month: April 2012

Re: [trinity-devel] Why do we support mlt?

From: "Timothy Pearson" <kb9vqf@...>
Date: Tue, 3 Apr 2012 16:41:04 -0500
>> Yes, I'm sure. The only qt installed in the chroot is tqt3.
>> Here was my build script:
>> makedepends=('sdl_image' 'libsamplerate' 'libdv' 'qt3' 'sox'
>> 'libxml2' 'gtk2' 'ffmpeg' 'frei0r-plugins' 'swig' 'python2'
>> "jack" "ladspa")
>> The only depends pulled in were:
>> Targets (5): gavl-1.2.0-2  libdc1394-2.1.3-2
>> opencv-2.3.1_a-4 frei0r-plugins-1.3-3  swig-2.0.4-3
>>   There isn't even a /usr/include/qt in the chroot...
> Perhaps the later versions have more intelligence built into the configure
> process.
> I still don't see why we support this package when the same is available
> upstream from the distro. We don't provide anything that depends upon
> mlt/mlt++.
> Darrell

As I mentioned before there were plans at one point to include kdenlive. 
mlt was imported at that point due to the fact that Ubuntu dropped
official builds of it.

If the upstream mlt project uses GIT and builds as-is under tqt3, I would
suggest importing the latest upstream release as a GIT submodule to
replace the badly outdated code currently in our GIT tree.