This is the mail archive of the
mailing list for the Cygwin project.
Re: Move zlib up one level, part 2
- To: <cygwin-apps at cygwin dot com>
- Subject: Re: Move zlib up one level, part 2
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Mon, 12 Nov 2001 08:32:19 +1100
- References: <20011111211701.GA23428@redhat.com>
----- Original Message -----
From: "Christopher Faylor" <firstname.lastname@example.org>
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.