<p dir="ltr">+1 to your plan. I spent a hours trying to figure out why things were wrong in F19 when I did yum install ardour. I think people expect that to get them the most recent package. </p>
<br><div class="gmail_quote">On Fri, May 8, 2015, 8:54 AM Nils Philippsen <<a href="mailto:nils@redhat.com">nils@redhat.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
with the advent of Ardour version 4, the question came up why the oldest<br>
available version 2 is packaged as "ardour" rather than the latest one:<br>
<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1216055#c15" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1216055#c15</a><br>
<br>
The reason for keeping version 2 around is that while later versions can<br>
migrate old sessions, some information is lost in the process. Ardour<br>
version 3 became ardour3 so people could install both versions 2 and 3<br>
side-by-side, and that the new package got reviewed instead of the old<br>
one (which would have been the case had I submitted an ardour2 package<br>
for review). In that vein I packaged version 4 as ardour4, also because<br>
ardour3-4.0.0 would have looked plain silly (despite that the session<br>
files are compatible between versions 3 and 4) and introducing a new<br>
major version replacing the old one with a substantially changed<br>
look-and-feel in an existing Fedora release is a big no-no.<br>
<br>
The question posed in the ardour4 review ticket is valid though, so I'd<br>
like to come up with a scheme for the future that achieves these<br>
objectives:<br>
<br>
- Installing "ardour" will always get you the latest available version<br>
(on a Fedora release -- e.g. F-20 won't get version 4 because the JACK<br>
package is too old).<br>
- Every major version gets its own package so side-by-side installs are<br>
possible, especially for occasions where the session format changes<br>
(like v2 -> v3).<br>
- Versions which are session-compatible with newer versions get retired<br>
from Fedora releases that aren't stable yet (e.g. v3 because the session<br>
format is the same as with v4).<br>
<br>
I'd do it like this (in Fedora >= 22):<br>
<br>
- Move version 2 to its own ardour2 package. This would get it<br>
re-reviewed but I guess that's a mere formality.<br>
- Reuse the ardour package as a meta-package which simply requires the<br>
latest versioned package.<br>
- Retire ardour3.<br>
<br>
What do you think?<br>
<br>
Nils<br>
--<br>
Nils Philippsen "Those who would give up Essential Liberty to purchase<br>
Red Hat a little Temporary Safety, deserve neither Liberty<br>
<a href="mailto:nils@redhat.com" target="_blank">nils@redhat.com</a> nor Safety." -- Benjamin Franklin, 1759<br>
PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011<br>
<br>
_______________________________________________<br>
music mailing list<br>
<a href="mailto:music@lists.fedoraproject.org" target="_blank">music@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/music" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/music</a></blockquote></div>