Re: [Mldonkey-users] Re: 2516 -> 2526

[Curtis Magyar]

On Thu, 2004-08-12 at 00:36 +0200, spiralvoice wrote: 
> Please test 2-5-27 before downgrading to 2-5-16.

Okay, now that everything is running smoothly here..  I'm going to try
to track down the bugs that are bothering me in 2.5-2x.

But first, I just have a couple of requests, if you could find it in
your heart. ;)

1) The most recent tarball available is 2.5-21, and the diff's leading
up to 2.5-27 are quite confusing to try to automate the process.  For
example:

  a) tar xvzf mldonkey-2.5.21.tar.gz
     cd mldonkey-2.5.21
     unzip -p /path/21-22.zip | patch -p4 -E  // Why is this one
different?
     unzip -p /path/22-23.zip | patch -p2 -E
     unzip -p /path/23-24.zip | patch -p2 -E
     unzip -p /path/24-25.zip | patch -p2 -E
     ...
     patching file src/networks/donkey/donkeyClient.ml
     Hunk #6 succeeded at 927 with fuzz 2.
     ...
     patching file src/networks/donkey/donkeyServers.ml
     Hunk #6 FAILED at 573.
     Hunk #7 FAILED at 668.
     ...

Hrmmm.  This should apply cleanly, should it not?


2) The instructions for pulling mldonkey from CVS have us grabbing CVS
head branch. The proper way to grab a release should be:

     CVS_RSH=ssh \
     CVSROOT=:ext:address@hidden:/cvsroot/mldonkey \
     cvs -z3 co -Pr release-2-5-27 mldonkey

instead of:
     CVS_RSH=ssh \
     CVSROOT=:ext:address@hidden:/cvsroot/mldonkey \
     cvs -z3 co -P mldonkey

( the key being -r <releasetag>  )

A tarball for each release would be just awesome.  Any chance you could
put one up on berlios for 2.5-27?

--
Curtis Magyar