From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23715 invoked by alias); 8 Jul 2005 02:05:07 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 23407 invoked by uid 22791); 8 Jul 2005 02:04:51 -0000 Received: from rwcrmhc13.comcast.net (HELO rwcrmhc12.comcast.net) (204.127.198.39) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 08 Jul 2005 02:04:51 +0000 Received: from [192.168.0.100] (c-67-172-242-110.hsd1.ut.comcast.net[67.172.242.110]) by comcast.net (rwcrmhc13) with ESMTP id <2005070802030801500s2emke>; Fri, 8 Jul 2005 02:03:08 +0000 Message-ID: <42CDDEDC.10908@byu.net> Date: Fri, 08 Jul 2005 02:05:00 -0000 From: Eric Blake User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Perl Win32::Shortcut screws up fork References: <7231C15EAC2F164CA6DC326D97493C8BA1C3FA@exchange35.fed.cclrc.ac.uk> <42CDD3B8.69B6AB98@dessent.net> <20050708011859.GB24841@trixie.casa.cgf.cx> <42CDD9CB.8390A097@dessent.net> In-Reply-To: <42CDD9CB.8390A097@dessent.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2005-07/txt/msg00293.txt.bz2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Brian Dessent on 7/7/2005 7:41 PM: > > Option B would be to write a C or C++ program to do the job of what > rebaseall currently does. That's even more work. True - there are many actions where scripts are just more convenient than full-blown programs, even though it introduces a dependency on the shell running the script. > > When I mentioned a static bash I was thinking of just making the base > package statically compiled, not having an alternative. Somehow I > imagined that this would make it a little faster too, but that's > probably going to be insignificant. > > I'm also wondering if the issue would ever come up in postinstall > scripts. Where before with ash or bash 2.x, we only required a working > Cygwin DLL, now any postinstall script has to also have these 4 core > DLLs in addition to the Cygwin DLL in place for any postinstall to > function. I haven't really though this through though, as to whether > this scenario matters. coreutils already requires libintl and libiconv since 5.2.1 days, so most useful actions in a postinstall script have already depended on having libraries available as part of Base. Based on several months of no complaints, I think we can discount the theoretical problems of this scenario. - -- Life is short - so eat dessert first! Eric Blake ebb9@byu.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCzd7c84KuGfSFAYARArF0AJ4vwRWQaQ81V3CJXULqyhEknMd5hQCg2OiV DLMDtNFn4FGM6Qe19fmb1XQ= =YTpA -----END PGP SIGNATURE----- -- 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/