On 04/19/2011 03:35 AM, Richard W.M. Jones wrote:
However this
is a big pain to maintain, not least because whenever a new
incompatible version comes along we have to apply for a new Unison
package to be added to Fedora(!)
Right, it's a shame there's no --protocol= flag.
I'd assume, being that Fedora likes to track upstream, we'd call the current build
'unison' and then the older binaries 'unison213' and 'unison227'?
On 04/19/2011 11:34 AM, Adam Williamson wrote:
FWIW, I'm in this mess too, but I was lazy and decided to just
hack up
the spec to build the version I need locally rather than do anything to
'properly' fix up the packages.
Oh, good. Is it 2.40.61? If so, the real work to be done is in combining the three
sub-builds into one .spec and then applying for a new 'unison' package?
-Bill
--
Bill McGonigle, Owner
BFC Computing, LLC
http://bfccomputing.com/
Telephone: +1.603.448.4440
Email, IM, VOIP: bill(a)bfccomputing.com
VCard:
http://bfccomputing.com/vcard/bill.vcf
Social networks: bill_mcgonigle/bill.mcgonigle