On Thu, May 31, 2018 at 01:45:19PM +0100, Tom Hughes wrote: > On 31/05/18 13:31, Richard W.M. Jones wrote: > > >Although this is very slightly dubious from a packaging point of view, > >I believe it's the best solution here. It means we can build multiple > >versions, we don't need to go through the new package review process > >every time upstream releases a new major version, and it'll make > >managing the package simpler at the cost of a somewhat more complex > >spec file. > > So long as the different versions don't conflict you don't actually > need a new review to package a different version - there is now an > automatic exception for that: > > https://fedoraproject.org/wiki/Packaging:ReviewGuidelines#Package_Review_Process > > and: > > https://pagure.io/packaging-committee/issue/637 But wouldn't a single package in fact be preferable, as it'll be simpler than maintaining multiple packages: - Everything visible in one spec file. - Only a single search to show all bugs. - Single method to find all supported unison versions. - Mass rebuild once. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://people.redhat.com/~rjones/virt-df/ _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/537ZLQDEPYIJSAU3S3ER54U42ISTDEPN/
