Il 03/03/23 19:00, Michael J Gruber ha scritto:
> SHORT VERSION
>
> The portmidi library in Fedora is at version 217, which is quite old.
> Upstream changed to a new version scheme, currently at 2.0.4, and
> dumped some subpackages. To serve the needs of different other
> packages, it would be easiest for me (as the portmidi maintainer in
> Fedora) and them to:
>
> - create a new package portmidi2
> - avoid any file conflicts between subpackages of portmidi and portmidi2 except:
> - allow file conflicts between portmidi{,2}-devel (.so, headers)
>
> This would allow to build packages against both versions (just not in
> the same container) by simply requiring the right devel package, and
> the libraries could coexist. Is this allowed by the packaging
> guidelines?
>
What about:
- create a compat-portmidi0 package and move current portmidi there
(bonus: mark it as deprecated)
- change frescobaldi to require the compat package until a fix is available
- update current portmidi package to v2
BTW, this is not the first time such a discussion arise and I think
FESCo / Packaging Guidelines must provide a definitive answer for this.
Mattia
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
