Separate cli, gtk and qt4 packages for 2.4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
avidemux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: avidemux
It may be too early for that, but I'm filing the bug prematurely because 2.4 isn't very far away.
Just wanted to notify the packagers that version 2.4 will require changes in packaging because it now includes three separate binaries: avidemux2_cli, avidemux2_gtk and avidemux2_qt4.
I think one should be able to install each binary separately.
The composition of the package can be broken apart as follows:
avidemux (transitional) -> avidemux-gtk
avidemux-cli
avidemux-gtk
avidemux-qt
all built from a single source.
One more thing to consider: version 2.4 includes two alternate build systems, the old autotools-based and the new cmake-based. Neither is perfect: the old one needs some juggling with ./configure options to build the qt4 version, and the new one doesn't see faac and x264, and tries to build without them.
I would advise packagers to start building preliminary packages of 2.4pre2, to be fully armed when 2.4 final arrives.
Here's a REVU package: http:// revu.tauware. de/details. py?upid= 6179
It might be treated as purely experimental, in anticipation of 2.4 final. But nevertheless it's there.
There are five binary packages built:
avidemux-common
avidemux-cli
avidemux-gtk
avidemux-qt4
avidemux (transitional) -> avidemux-gtk
I chose CMake, as it's a newer addition and will probably be the main focus of upstream developers, even though it requires a dpatch for the configure system to find FAAC and x264.