Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <414F7F7E.AF000A9F@dessent.net> Date: Mon, 20 Sep 2004 18:10:22 -0700 From: Brian Dessent Organization: My own little world... MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: [APPS] ping python maintainer (and others) - Launching cygwin apps from cmd.exe vs. softlinks in /bin References: <20040920154802.GN6525@trixie.casa.cgf.cx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com 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...) Brian [1] And technically you'd need to remove it with a preremove script, otherwise you'd get a broken link hanging around in your path after you removed the package with setup.exe. -- 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/