Overview
waiting for mlt6 compat package for kdenlive
I submitted it to KDE:Applications but they declined it with no comment. sr#893745 and sr#893744
The comments are in the other request: https://build.opensuse.org/request/show/891858
libmlt is a multimedia library, it has nothing to do in KDE:Applications.
and for the record, you declined the libmlt6 requests:
https://build.opensuse.org/request/show/891248
https://build.opensuse.org/request/show/890711
So you're perfectly aware of the situation.
libmlt6 is exclusively for the use of kdenlive, which although it's a multimedia application, lives in KDE:Applications. The only other application that uses libmlt is shotcut, the kdenlive developers seem to have given up on their mlt7 branch. I don't wish to maintain libmlt6 and in fact there will never be an update and when kdenlive catches up with mlt7 it will become redundant.. Therefore it should live in KDE:Applications with kdenlive. I still have the package and a kdenlive that just requires pkgconfig mlt instead of requiring libmlt-devel. Just say the word and I'll submit them again
I'm sure Luigi is fine with maintaining the package in multimedia:libs
I really don't care, I just want the libmlt package to remain as is. There's no reason why the two melts should have to exist together, they must remain mutually exclusive. Don't forget to fix kdenlive. sr#893745
The comments are in the other request: https://build.opensuse.org/request/show/891858
I never saw that request until now.
If you do not want to maintain libmlt6, there are other ways to express it, even if it lives in multimedia:libs.
i586: python3-mlt: - libmlt6 - libmlt x86_64: python3-mlt: - libmlt6 - libmlt
This means: libmlt and libmlt6 source packages both produce binary packages with the same name; this conflicts with each other as only one (random) variant would be published.
Each source package needs to produce unique binary package names
I had to conflict python3-mlt < version and leave the libmlt6 name as python3-mlt. Now mlt6's python package simply gets upgraded and vice versa
you cannot have two source packages produce the same binary package name.
Request History
plater created request
- Removed alternatives from melt sub package
- Update to version 7.0.1 and fix install conflicts
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
licensedigger accepted review
ok
dimstar_suse added openSUSE:Factory:Staging:adi:19 as a reviewer
Being evaluated by staging project "openSUSE:Factory:Staging:adi:19"
dimstar_suse accepted review
Picked "openSUSE:Factory:Staging:adi:19"
dimstar accepted review
dimstar_suse accepted review
Staging Project openSUSE:Factory:Staging:adi:19 got accepted.
dimstar_suse approved review
Staging Project openSUSE:Factory:Staging:adi:19 got accepted.
dimstar_suse accepted request
Staging Project openSUSE:Factory:Staging:adi:19 got accepted.
libmlt6 should be sorted now but the Conflicts line in libmlt.spec prevent coinstalling both. The kdenlive devs would like to install both to port their code
(comment updated)
You already have the exclusive pkgconfig build requires. If you can cope with using melt6 instead of melt I can remove that conflict and remove the devel file conflicts. I'm actually confused as to why you need both installed. When I build against wxWidgets for instance all the devel files are mutually exclusive. I don't have time for this, when lilypond no longer used the current texinfo and guile I had to create packages for it as the lilypond maintainer.
I removed the melt symlink, all the unneeded conflicts lines and submitted a coinstallable package to factory.
kdenlive will need a small fix to look for /usr/bin/melt6.
only the python bindings are not coinstallable (while they technically can) because of the conflicts line in libmlt.
The python bindings look like they aren't used by any package, I don't think they are even necessary for libmlt6
The KDE CI tracks both the development and stable branches. The stable one will use melt 6, the dev one will use melt 7 soon™