Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<42CDDF38.CE18B009@dessent.net>
Date:	Thu, 07 Jul 2005 19:04:40 -0700
From:	Brian Dessent <brian AT dessent DOT net>
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Perl Win32::Shortcut screws up fork
References:	<7231C15EAC2F164CA6DC326D97493C8BA1C3FA AT exchange35 DOT fed DOT cclrc DOT ac DOT uk> <42CDD3B8 DOT 69B6AB98 AT dessent DOT net> <42CDD834 DOT 7060503 AT byu DOT net>
X-Spam-Report:	-5.9/5.0 ---- Start SpamAssassin results * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] * 0.0 AWL AWL: From: address is in the auto white-list ---- End SpamAssassin results
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

Eric Blake wrote:

> Or, you could make rebaseall a #!/bin/ash script, which would require that
> we never kill ash from the distribution, while freeing you from bash's
> dynamic linking.

Ah, hadn't thought of that.  This seems like the best short-term
solution, since it involves minimal changes.  The only potential problem
is that it requires that the user upgrade their 'ash' package, but they
would have to also presumably upgrade their 'rebase' package too
anyway.  I don't think anyone here wants to try to support people that
refuse to upgrade certain packages to 'Curr', so it's not a big deal.

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/

- Raw text -