https://bugzilla.redhat.com/show_bug.cgi?id=2137159
--- Comment #3 from Mads Kiilerich mads@kiilerich.com --- (In reply to Nils Philippsen from comment #1)
NB^2: The reason for having a separate package for this new version is so people can choose which version of Ardour to use for existing and new projects.
As mentioned in https://src.fedoraproject.org/rpms/ardour6/pull-request/5 (currently offline):
I think that putting the first part for the version number in the package name is a bad idea. The package name should just be "ardour".
* Ardour doesn't use semantic versioning. The step from 6.9 to 7.0 is not necessarily bigger than the step from 7.0 to 7.1 . Allowing side-by-side installation only when the first number changes will in general miss the point and just "work" randomly.
* That is not how we do in Fedora. Unless there are very good reasons, we package the latest and greatest version of end user software. We do for example not have two versions of for example OpenOffice, Firefox, GIMP, or Inkscape. It is unclear why this particular package needs it, and what problem this is solving.
* Ardour 7 can read (and upgrade) Ardour 6 projects. There is no particular good reason these two versions should be installed side-by-side. Supporting evidence: Upstream no longer makes Ardour 6 (easily) available for download.
* Having the version number in the package does that a trivial update to a new major version requires a new package review, for no good reason. That can potentially delay upgrades and put extra load on the review process.
* Having two versions side by side raise tricky upgrade questions. The general user experience should of course be that Ardour automatically gets upgraded to Ardour 7 ... or at least that it is installed automatically so it is available for launch, next to Ardour 6. This spec doesn't handle that at all.