[Top][All Lists]

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

Re: [wdiff-bugs] Build problems fixed, please test for 0.5.4 release

From: Denver Gingerich
Subject: Re: [wdiff-bugs] Build problems fixed, please test for 0.5.4 release
Date: Sat, 23 Jun 2007 00:53:22 -0400

On 6/22/07, Santiago Vila <address@hidden> wrote:

The current code does not pass my test for well-behaved makefiles:

cvs -z3 -d:pserver:address@hidden:/sources/wdiff co wdiff
cp -a wdiff wdiff.orig
cd wdiff
make distclean
cd ..
diff wdiff.orig wdiff

The output for the last commmand should be empty, but it's not:
I believe it's the GNU standards who say this should be empty, but I'm not
completely sure. I would call it a highly desirable thing anyway.

Does this work on the stock wdiff 0.5?  What about 0.5g
(http://wdiff.progiciels-bpi.ca/archives/wdiff-0.5g.tar.gz)?  If the
resulting directories are the same with 0.5g, then I broke something.
If the results are similar, then I will leave the behavior as-is for
this release and fix it later (since the new release is intended to be
equivalent to 0.5g, except with the appropriate copyright information,
mailing list addresses, FSF address, etc. updated).

Another thing which I noticed: It would be a good idea to send the .pot
file for version 0.5.4 to the Translation Project Robot, and wait a few
days, so that translators have some opportunity to update the translations.

I will look into this.  I haven't worked much with this translation
system before so it would be good to know more about.


./configure; make dist


make: *** No rule to make target `README-alpha', needed by `distdir'.  Stop.

which I think it should not happen.

You're right.  The reason this happens is that I deleted the
README-alpha file that 0.5g has because it did not seem relevant
anymore.  I will remove the dependency and re-release the source.

BTW: Would be possible to generate a protoype tarball for 0.5.4pre?
I would like to be sure that the final tarball will not include CVS

I will be sending a message pertaining to that request shortly.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]