Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Message-ID: <032f01c16af8$57ff5730$0200a8c0@lifelesswks> From: "Robert Collins" To: References: <20011111211701 DOT GA23428 AT redhat DOT com> Subject: Re: Move zlib up one level, part 2 Date: Mon, 12 Nov 2001 08:32:19 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 11 Nov 2001 21:38:11.0886 (UTC) FILETIME=[2981D4E0:01C16AF9] ----- Original Message ----- From: "Christopher Faylor" To: Sent: Monday, November 12, 2001 8:17 AM Subject: Move zlib up one level, part 2 > I have the cinstall makefile modified but the next question is > "How should I do this?" > > My preference is to be naughty and just move the cvs directory > itself. That way any cvs history in zlib is carried forward. And all CVS versions of Makefile.in except HEAD die horribly. No thanks. > This would mean that I'd have to modify the sources and Makefiles > on at least three branches, which I'm willing to do. I'm just > wondering if I will screw anyone up if I do this. Yes, you'll screwup Makefile.in, not per tag, but per revision. > The alternative is to create a new winsup/zlib directory. I believe > that would mean that everyone would have to use the -P option when > updating their directories to cause the empty directory to be > automatically deleted. Yes. They'd have to anyway regardless of the way you do the move. You could take a copy of thezlib dir, and use cvs delete to delete the old one - that way you'll have the history on the new dir, and a checkout -D in cinstall will continue to work. -Rob