Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
X-Apparently-From:	<earnie?boyd AT yahoo DOT com>
Message-ID:	<3BD6C60D.B37C39EE@yahoo.com>
Date:	Wed, 24 Oct 2001 09:45:49 -0400
From:	Earnie Boyd <earnie_boyd AT yahoo DOT com>
X-Mailer:	Mozilla 4.77 [en] (WinNT; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	egor duda <cygwin-developers AT cygwin DOT com>
Subject:	Re: Need name and functionality suggestions for a new utility
References:	<20011024005137 DOT A29851 AT redhat DOT com>
	<007f01c15c7b$84f86a50$65f504c0 AT sos> <3BD6AFAF DOT 8DC42F4A AT yahoo DOT com> <539145530 DOT 20011024170752 AT logos-m DOT ru>

egor duda wrote:
> 
> Hi!
> 
> Wednesday, 24 October, 2001 Earnie Boyd earnie_boyd AT yahoo DOT com wrote:
> 
> EB> Ok, for item 1 you simply
> 
> EB> * mkdir /dll-1.3.3
> EB> * mkdir /dll-test
> EB> * move /bin/cygwin1.dll to /dll-1.3.3
> EB> * install your test cygwin1.dll to /dll-test
> EB> * cp /etc/profile /etc/profile-rls
> EB> * cp /etc/profile /etc/profile-test
> EB> * add the /dll-1.3.3 to the PATH settings in the /etc/profile-rls.
> EB> * add the /dll-test to the PATH settings in the /etc/profile-test.
> EB> * cp /cygwin.bat /cygwin-rls.bat
> EB> * cp /cygwin.bat /cygwin-test.bat
> EB> * add a copy of /etc/profile-rls to /etc/profile in the cygwin-rls.bat
> EB> * add a copy of /etc/profile-test to /etc/profile in the cygwin-test.bat
> EB> * issue - executing cygwin binaries outside of a Cygwin enabled shell.
> EB> * resolution - set the PATH manually before executing binaries.
> 
> EB> This gives the isolation you need for the current releases of Cygwin
> EB> without fancy manipulations.
> 
> EB> Given the simplicity of the isolation above, are differing mount tables
> EB> necessary?
> 
> 1. somebody may want to have, say, /usr/include different across
> his cygwin "environments" or "profiles".

Ok

* mv /usr/include /usr/include-rls
* install your test versions to /usr/include-test
* ln -s /usr/include-rls /usr/include (or create a mount entry).
* modify your cygwin-rls.bat and cygwin-test.bat files to do the proper
forced symlink (or forced mount entry).

> 2. changing $PATH is not enough. for example, system() calls /bin/sh,
> and doesn't perform $PATH lookup.
> 

That's fine, in the scenario I described above the part that changed was
the cygwin1.dll not the sh.exe binary.  I just don't get why anything
else is necessary to isolate a test version of cygwin1.dll.

If a differing mount table is desired, and I do see potential PRO's for
such a thing then a CYGWIN option "mountkey=foo" should be added and a
tool "cygremount" that copies the "mount v2" keys to a user specified
value be given.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

- Raw text -