Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Wed, 24 May 2000 12:10:44 -0400
Message-Id: <200005241610.MAA01721@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: new setup in cvs


I've just checked in my biggie patches to do these:

	* tar.c: New file; built-in tar using zlib.
	* tar.h: New file; header for same.
	* ctar.c: New file; test program for same.
	* Makefile.in: add built-in tar, remove tar.exe and gzip.exe
	* path.c (pathcat): convert slashes and canonicalize, instead of aborting
	* setup.c (tarx): add support for built-in tar
	(main): accept unix-style slashes, check root dir for drive letters,
	warn about installing in /, make sure cwd is empty for internet installs,
	defer mounts to end of install, support built-in tar.

One advantage I didn't think of before is that by using an internal
tar, we can defer messing with the mount table until after we know
everything was installed correctly.  Changing the mount table is now
the *last* thing setup does.

My next chunk will hopefully include these goals:

* internalize the remaining .exes
* use unique name and shared memory area for cygwin1.dll
* call cygwin1.dll functions directly (to internalize exe's above)
* default mount points to previously installed text/binary setting

This should also let setup run with an incompatible cygwin DLL already
running in the system.