| Summary: | mlt : Conflicts with freeze | ||
|---|---|---|---|
| Product: | Fedora | Reporter: | Michael Schwendt <mschwendt> |
| Component: | mlt | Assignee: | Zarko Pintar (grof) <zarko.pintar> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | dan |
| Priority: | P5 | ||
| Version: | 14 | ||
| Hardware: | All | ||
| OS: | GNU/Linux | ||
| namespace: | |||
Reported to upstream. I recently changed the name from inigo to melt and chose it for a few reasons: the pronunciation of acronym MLT, easy to remember, and not found in my Debian/Ubuntu and Arch Linux repositories. As a result of the change, there was a dependent project to update and some community education and awareness involved. What does a distro or Fedora do when upstream does not want to change and this happens? Surely, this isn't the first. Do you change the package to install the executable with a different name? As a last resort, Fedora packagers can request approval for explicitly making a package conflict with another package through RPM's "Conflicts" tag. A little bit better than an implicit/hidden conflict. Here, at RPM Fusion, there is no Packaging Committee, and I believe the packager may add such a Conflict tag without prior consent. Of course, renaming executables in order to not overload the crowded /usr/bin namespace would be the preferred solution. For upstream projects, a wise decision is to add some prefix to file names. Such as the project name, e.g. mtl-melt or mlt-framework-melt, even if that doesn't look as cool, but it helps a lot with pollution of file locations such as in /usr/bin. For mlt, it already tries to occupy the "mlt" and "mlt++" namespaces for /usr/include, /usr/lib, as well as SONAMEs and pkgconfig files. https://fedoraproject.org/wiki/Packaging:Conflicts I am going to rename the executable as mlt-process and install a 'melt' symlink that can be disabled at configure time for Fedora. I added a configure option --rename-melt=foo so you can name it as you like. This avoids a standard install getting a symlink and two equivalent executables. The next release will come at the end of this month. |
=> mlt-0.4.0-3.fc11.src.rpm => mlt-0.4.0-3.fc11.i586 in rpmfusion-free-development-i386 File conflict with: freeze-2.5.0-10.fc12.i586 /usr/bin/melt