Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="US-ASCII"
Subject: RE: Suggestion for run (with patch)
Date: Mon, 9 Apr 2007 22:00:04 +0100
Message-ID: <7231C15EAC2F164CA6DC326D97493C8B02F8FE3E@exchange35.fed.cclrc.ac.uk>
In-Reply-To: <20070409145533.GA8977@ednor.casa.cgf.cx>
References: <7231C15EAC2F164CA6DC326D97493C8B02F8FE34@exchange35.fed.cclrc.ac.uk> <20070409145533.GA8977@ednor.casa.cgf.cx>
From: "Adye, TJ \(Tim\)" <T.J.Adye@rl.ac.uk>
To: <cygwin@cygwin.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

Hi Christopher,

Christopher Faylor wrote:
>
> I don't see any reason to include a non-cygwin version of a 
> program in the *cygwin* distribution.  If you don't have 
> cygwin1.dll in the path, then you aren't running in a cygwin 
> environment.
> 
> This is not to say that I don't understand perfectly why 
> someone might want to not use cygwin or how wonderful it 
> might be not to use cygwin1.dll.  This just isn't an issue we 
> need to deal with here.

This is nothing to do with knocking Cygwin. I'm talking about using
run-native.exe to start Cygwin programs. However, when starting Cygwin
programs from Windows, I find it clearer to setup the PATH (and perhaps
start ancillary programs like Exceed) before invoking a Cygwin program.
Yes, I could probably change things around to work with the Cygwin
version of run (though for my use cases, that would be more convoluted),
but a non-Cygwin version used to be part of the package, and solved the
problem neatly. I am just restoring the functionality, and giving people
another option.

Also, since the run package is now part of Cygwin (and doesn't seem to
be maintained elsewhere), it seems an unnecessary confusion to maintain
two branches. If you really don't like having anything not linked with
cygwin1.dll as part of the distribution, then how about taking the
source-code updates and leaving the extra executable out of the
distribution - though that would be a pity for people like me who find
this the best way to start Cygwin programs.

As I said before, run-native.exe doesn't need to live in /usr/bin, and
could be called something else. But it is convenient to have available
as a way to start Cygwin programs (I have been looking to releasing some
other software to help with this, but I'm still tidying that up...).

Tim.

===========================  cut here  ============================
 Tim Adye      T.J.Adye@rl.ac.uk       http://hepunx.rl.ac.uk/~adye
 BaBar/Atlas Groups, Particle Physics Dept, Rutherford Appleton Lab

--
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/