[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Incompatible Unison update (and solution?)



2008/2/21 Toshio Kuratomi <a badger gmail com>:
> Stephen Warren wrote:
>  > So, I'm a Fedora packager. I can look into packaging the old Unison
>  > version alongside the bleeding-edge version. I imagine (hope) it'd be as
>  > simple as pulling the old .spec file from CVS and renaming the package.
>  >
>  It could be but probably isn't.  When installing an old version we want
>  the packages to be parallel installable.  With something like unison,
>  this is easy to show -- I have my laptop which I need to keep synced
>  with my computer at work and computer at home.  Those two computers have
>  different versions of unison installed.  Therefore my laptop needs to
>  have both of those versions.
>
>  Taking a brief glance at the unison spec file it looks like you can just
>  rename most files from unison* to unison2.13* but I haven't looked
>  inside the source files to see that this is the only necessary change.
>
Wouldn't the remote unison be expecting the binary to be called
unison? To make the compat-* operation seamless, /all/ unison packages
might have to use the alternatives system.

(mea culpa, I was involved in pushing the new unison into Fedora)

-- 
Michel Salim
http://hircus.jaiku.com/


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]