X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 18 Aug 2010 22:17:45 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: "run" changes behavior with cygwin-17.6
Message-ID: <20100818201745.GH11340@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <4C6C1582 DOT 1080801 AT acm DOT org> <20100818182412 DOT GA22698 AT ednor DOT casa DOT cgf DOT cx> <AANLkTikBTgg9M=xuZ4S2VkNU+Zr=hy3C=_Tr8BPj5baD AT mail DOT gmail DOT com> <20100818185421 DOT GC22698 AT ednor DOT casa DOT cgf DOT cx> <20100818191340 DOT GB11340 AT calimero DOT vinschen DOT de> <20100818191906 DOT GD22698 AT ednor DOT casa DOT cgf DOT cx> <20100818192238 DOT GA27567 AT ednor DOT casa DOT cgf DOT cx> <20100818193446 DOT GC11340 AT calimero DOT vinschen DOT de> <20100818194152 DOT GE11340 AT calimero DOT vinschen DOT de> <4C6C39A8 DOT 6000402 AT cwilson DOT fastmail DOT fm>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4C6C39A8.6000402@cwilson.fastmail.fm>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

On Aug 18 15:51, Charles Wilson wrote:
> On 8/18/2010 3:41 PM, Corinna Vinschen wrote:
> 
> >Chuck, btw., the function setup_win_environ() in run.c can easily be
> >replaced with `cygwin_internal (CW_SYNC_WINENV);'
> 
> Yes, I was just looking at that. I think setup_win_environ (or its
> guts before some early refactoring) pre-dated CW_SYNC_WINENV.
> 
> Before removing it, I'll have to verify some things -- like whether
> that-cygwin-fork-we-don't-mention has CW_SYNC_WINENV, and how hard
> it would be to add if not -- since I want run to work "over there"
> too.

CW_SYNC_WINENV is available since May 2006.  That's Cygwin 1.5.20-1.

> With respect to the orginal discussion that spawned this thread, I'm
> going to hold off on any changes to run/run2/cygutils until a
> consensus is reached regarding:
>   1) what's going to happen "inside" cygwin wrt win32 cwd;

I'm not sure yet.  Maybe we should really go cgf's idea to stick
to the Win32 CWD, as long as chdir isn't called the first time.

>   2) what new APIs are provided

In PM we agreed on my suggestion.  I just have to test and document
it first...

>   3) and a project on how soon an official 1.7.7 will be released with
>      those changes

I think 1.7.7 will be released rather very soon.  Maybe this weekend.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple