Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: ericblake AT comcast DOT net (Eric Blake)
To: cygwin AT cygwin DOT com
Subject: Re: ruby-1.8.3: ginstall
Date: Tue, 11 Oct 2005 18:25:14 +0000
Message-Id: <101120051825.23861.434C0389000D381100005D3522007340760A050E040D0C079D0A@comcast.net>

> On Oct 11 12:52, Yaakov S (Cygwin Ports) wrote:
> > While building a ruby module (extconf.rb method) with ruby-1.8.3,
> > INSTALL is defined as "/usr/bin/ginstall -c".  There's no ginstall on
> > Cygwin, just install.

> On my machine I had a ginstall for some reason and I even don't know
> anymore where it came from.

coreutils internally builds ginstall.exe, then installs it to
install.exe (otherwise, imagine the confusion if you type
make install, but it builds the one binary instead of installing
everything in coreutils).  Should I provide a new coreutils
release that provides g<name> variants of the various
coreutils as links to the <name> version, so that cygwin
would then indeed have a ginstall in addition to install?

--
Eric Blake



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/