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 Date: Sun, 11 Nov 2001 16:33:18 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: Move zlib up one level, part 2 Message-ID: <20011111213318.GA23506@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <20011111211701 DOT GA23428 AT redhat DOT com> <032f01c16af8$57ff5730$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <032f01c16af8$57ff5730$0200a8c0@lifelesswks> User-Agent: Mutt/1.3.23.1i On Mon, Nov 12, 2001 at 08:32:19AM +1100, Robert Collins wrote: > >----- 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. Interesting point. So interesting you needed to make it twice, I guess. >> 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. Nope. cgf