Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Mon, 20 Sep 2004 21:17:05 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: [APPS] ping python maintainer (and others) - Launching cygwin apps from cmd.exe vs. softlinks in /bin Message-ID: <20040921011705.GH11505@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20040920154802 DOT GN6525 AT trixie DOT casa DOT cgf DOT cx> <414F7F7E DOT AF000A9F AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <414F7F7E.AF000A9F@dessent.net> User-Agent: Mutt/1.4.1i On Mon, Sep 20, 2004 at 06:10:22PM -0700, Brian Dessent wrote: >Christopher Faylor wrote: > >> On Mon, Sep 20, 2004 at 04:09:50PM +0100, Dave Korn wrote: >> >Now, in this particular case "python.exe" is a cygwin old-style >> >softlink rather than a windoze .lnk-style shortcut. >> >> Because that's how setup.exe sets up symlinks. PTC. > >Alternatively, the postinstall[1] script could be used to setup the >symlink using 'ln', instead of including it in the tarball and expecting >setup.exe to make it. Wouldn't that make everyone happy? (Except >perhaps the python maintainer, who now has an extra step...) It's better to just fix setup.exe. cgf -- 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/