Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
From: "Robert Collins" <robert DOT collins AT syncretize DOT net>
To: "'Charles Wilson'" <cwilson AT ece DOT gatech DOT edu>,
   "'Conrad Scott'" <Conrad DOT Scott AT dsl DOT pipex DOT com>
Cc: <cygwin-developers AT cygwin DOT com>
Subject: RE: System-wide mutexes and pthreads
Date: Fri, 14 Jun 2002 00:22:10 +1000
Message-ID: <009c01c212e5$b4de6640$0200a8c0@lifelesswks>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
In-Reply-To: <3D07C4E0.2050603@ece.gatech.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000



> -----Original Message-----
> From: Charles Wilson [mailto:cwilson AT ece DOT gatech DOT edu] 
> Sent: Thursday, 13 June 2002 8:02 AM

> This reminded me of something....
> 
> Robert -- once upon a time the idea was bandied about to create a 
> "subcygwin" static library that used only native, non-cygwin calls to 
> directly access the cygwin mount table and sort of duplicate the 
> functionality of (only) these two functions from cygwin.dll:
> 
>    cygwin_conv_to_full_win32_path
>    cygwin_conv_to_posix_path
> 
> [I'm sure this code is already in setup.exe's codebase -- somewhere]. 

Well, something equivalent is. It's still getting worked on to be more
loosely coupled. The actual thread you are referring to was on a
different program that setup, but yes I do recall it. The goal with
setup is to produce a library that cygcheck can use to sanity check the
install, that encapsulates the program logic of setup. (i.e. package
listings, installed files, etc etc etc). This is also underway, although
I imagine that Chris will have a small hernia when I ask for cygcheck to
use the STL.

> Anyway, I lost track of what happened with this proposal.  Was it 
> decided that this was a bad idea, and that
>    setup
>    rebase
>    strace
>    cygcheck
> should all continue to duplicate cygwin-like path translation 
> independently, or did the idea just fizzle for lack of volunteers?

Fizzled... Work on setup modularisation progress nicely given the list
of TODO's. Work on the idea of a specific library (which as I mention
above, was not targeted at cygcheck or setup) for mount point
understanding fizzled.

Rob