On Mon, Jun 15, 2015 at 01:03:58PM +0200, Miroslav Suchý wrote: > Dne 7.5.2015 v 10:17 Richard W.M. Jones napsal(a): > > For this reason, Fedora packages three different Unison branches in > > separate packages: > > > > - unison213 (currently Unison 2.13.16) > > - unison227 (currently Unison 2.27.57) > > - unison240 (currently Unison 2.40.128) > > - There was a "unison" package, but it is retired > > > > We don't package the latest upstream (Unison 2.48.3) at all[1]. > > > > For comparison, Debian packages: > > > > - unison2.27.57 > > - unison2.32.52 > > - unison (which contains 2.40.x) > > - unison-all, a meta-package, which pulls in all of the above > > > > AFAICT Debian also does not package the latest upstream version. > > > > So you can see that someone who needed to synchronize across Fedora > > and Debian machines would have two compatible choices: > > > > - Fedora unison227 <-> Debian unison2.27.57 > > - Fedora unison240 <-> Debian unison > > BTW Do you talk to Debian maintainers and e.g. synchronize which next version you will be packaging so Linux word get > matrix with more compatible versions available on servers? I do know the Debian maintainers, since most OCaml users meet up once a year, but I've not talked to them about this. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
