X-Spam-Check-By: sourceware.org Message-ID: <461AAA69.70322D19@dessent.net> Date: Mon, 09 Apr 2007 14:04:41 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Suggestion for run (with patch) References: <7231C15EAC2F164CA6DC326D97493C8B02F8FE34 AT exchange35 DOT fed DOT cclrc DOT ac DOT uk> <20070409145533 DOT GA8977 AT ednor DOT casa DOT cgf DOT cx> <7231C15EAC2F164CA6DC326D97493C8B02F8FE3E AT exchange35 DOT fed DOT cclrc DOT ac DOT uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com "Adye, TJ (Tim)" wrote: > 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...). If you really want a compromise solution, you could modify run to not depend on cygwin1.dll at link-time but instead LoadLibrary() it at runtime, and if that fails fall back to whatever the native version would have done. Thus you get a single executable that understands posix paths if the DLL is in the PATH and still allows to you "run c:\cygwin\bin\bash.exe" (or whatever it is that you're currently doing) if the DLL is not in the PATH. Though that itself may cause confusion... Brian -- 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/