Re: [rdiff-backup-users] spec changes for librsync on Rh 7.3

[Ben Escoto]

>>>>> "JC" == Joe Cooper <address@hidden>
>>>>> wrote the following on Sat, 28 Sep 2002 18:46:27 -0500

  JC> I'll look into it.  But it isn't really a problem with librsync,
  JC> it is a problem of incompatible changes made to both automake
  JC> 1.5 and 1.6 from 1.4.  In some circumstances, it seems,
  JC> something that builds successfully using 1.4 won't build with
  JC> 1.5/1.6 and vice versa, so in order to make the move up to later
  JC> revisions Red Hat has included all three with version tags at
  JC> the end of the executables.  I reckon everyone is just doing
  JC> their best not to break existing software while allowing new
  JC> software to build.  (Squid went through this debate recently,
  JC> which is the only reason I was aware of the incompatibilities.)

I had heard of the incompatibilities (in fact I have been blaming them
for too much...), but there must be some better way to behave on
RPM-less systems than to exit with some cryptic error.  Oh well, I
will leave it to the librsync people and be glad for python's
distutils.

  JC> I can provide packages built against clean, fully erratified, RH
  JC> 7.2 and 7.3 systems.  I've also got 7.1 and 6.2 build
  JC> environments, but they are a bit old and hairy and might run
  JC> into similar issues.

Sounds great, thanks.  No need to bother yourself making more than one
or two versions though.


-- 
Ben Escoto

pgp64aHaQsilH.pgp
Description: PGP signature