This is the mail archive of the
mailing list for the Cygwin project.
Re: mmroff is installed with a bad path to perl after installing groff
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 23 Aug 2007 18:13:15 -0400
- Subject: Re: mmroff is installed with a bad path to perl after installing groff
- References: <firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
Mike Burns wrote:
mmroff is a perl script that is installed along with groff.
I'm not sure if cygwin setup is supposed to detect dependencies, but
it doesn't realize that perl is required.
After installing perl, the path to the perl interpreter is incorrect
in the mmroff script.
I'm also not sure if this is the responsibility of cygwin or groff
but the mmroff script tries to find perl in /usr/local/bin instead of
That would be a packaging error. One might also say that the missing
dependency is a packaging error but I think it also raises a more important
question - does it make sense to have Perl pulled in by dependencies from
the "Base" category of packages (i.e. those installed by default even if the
user selects nothing else)? This is a rhetorical question though. It has
been asked and answered before. The answer was "no". So it would seem
that if 'mmroff' has a dependency on Perl and 'groff' will be pulled in
as part of a base installation, 'mmroff' needs to be pulled out into its
own package if Cygwin is going to continue to provide it. There may be
other options as well, which the 'groff' maintainer is free to explore.
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html