[Top][All Lists]

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

Re: [wdiff-bugs] 'make install' does not install 'mdiff'

From: Denver Gingerich
Subject: Re: [wdiff-bugs] 'make install' does not install 'mdiff'
Date: Fri, 9 Nov 2007 14:25:03 -0500

On Oct 9, 2007 4:37 PM, Benno Schulenberg <address@hidden> wrote:
> Hi,
> Upon installation, wdiff forgets to install the mdiff program,
> although it does install the man page and Info document for it.

As I have incorporated the code from wdiff 0.5g into CVS, I have been
copying its functionality as I go along.  Since wdiff 0.5g doesn't
install the mdiff binary, neither does the current CVS version of

The logic behind this is the assumption that there were good reasons
to do things the way wdiff 0.5g does them so we should do them the
same way in the new wdiff version.  However, I realize that this may
not be a wise assumption to make in all cases (and particularly in
this one) so I appreciate comments on behavior that appears incorrect.

I haven't taken the time to look at mdiff to see what it does and why
it should be installed with wdiff.  I wouldn't want to install mdiff
with wdiff if the functionality of mdiff is already present in another
package.  I will investigate this and make the appropriate changes:
removing mdiff from the wdiff package completely, installing all parts
of mdiff (binary and docs) with wdiff, or leaving the mdiff source in
wdiff but not installing it with wdiff by default.

> In wdiff.texi the --statistics option for mdiff is described twice.
> Also --help and --version occur twice; their second occurrences are
> straight copies from the wdiff section, and mistakenly mention -h
> and -V as synonyms -- these work for wdiff, but not for mdiff.
> The Info doc further mistakenly mentions -c as synonym for
> --ignore-case (should be -i, also for wdiff), and -a as synonym
> for --autopager (should be -A, but only for mdiff).  It looks like
> there may be several more errors like this.
> This all is about the version in CVS.

Thanks for reporting those.  I will correct those and scan the
documentation for similar errors.

I apologize for the significant lag in my response.  This is an
exceptional case.  Usually you can expect a response from me within a
day or two.


reply via email to

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