This request is superseded by
request 862607
(Show diff)
Overview
Request 862606 superseded
- Split out the Cakewalk mimetype into a seperate package, it
breaks co-installability of several versions
- Created by wolfi323
- In state superseded
- Superseded by 862607
Loading...
Request History
wolfi323 created request
- Split out the Cakewalk mimetype into a seperate package, it
breaks co-installability of several versions
Is this file really used by the library - not rather by the desktops to decide what program to open the files of a specific mime type with? sounds more like this file should be in the main package
The library doesn't seem to use it, no.
But the main package is not installed by default, it only contains some (mostly command line) tools that use the library.
There are other (GUI) applications that use the libraries (and support reading/writing Cakewalk files therefore) that don't need the drumstick main package installed.
the mime typedefinition is basically used by xdg-open/nautilus/dolphin to allow you to define an application to use when opening a specific file type. In this case, it still sounds like the tools in the main package would be meant to be used for that purpose, no?
Sure, but what I wanted to say is that there may be other applications that can be used to open files of this type. kmidimon (a separate package, that also uses/requires libdrumstick-file) is one of them, it has this in its desktop file: MimeType=audio/midi;audio/x-midi;audio/cakewalk;
As the file was part of libdrumstick-file1 before, the mimetype will just "disappear" on users' systems if they didn't install the main package manually.
Also, moving it to the main package would make it conflict with libdrumstick-file1. Wouldn't this also violate the SLPP? It would prevent to keep libdrumstick-file1 (if you have the main package installed) which might still be used/needed by other applications.
These are the reasons why I split it out in a separate package instead of moving it in the first place.