X-Spam-Check-By: sourceware.org Message-ID: Date: Tue, 1 May 2007 09:50:31 -0400 From: "Lev Bishop" To: cygwin@cygwin.com Subject: Re: [Ping Python maintainer]: enhancement request In-Reply-To: <20070501133951.GB17841@trixie.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070501120623.GA3824@tishler.net> <20070501133951.GB17841@trixie.casa.cgf.cx> Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On 5/1/07, Christopher Faylor wrote: > On Tue, May 01, 2007 at 08:06:23AM -0400, Jason Tishler wrote: > >OK. Should I copy or make a hard link? > > Before you do this, I have a question. Why is this important now when you've > apparently been doing this for many years? This isn't the only package which > makes symlinks to executables. And, since, AFAIK, setup.exe doesn't understand > hard links it means that you really do have to make a copy. If you make a copy > you stand the chance of having python.exe out of sync with the thing that it is > supposed to be pointing to. You could avoid that particular problem by making a hardlink in a postinstall script, right? Lev -- 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/