Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-ID:	<36DEB260.C6BF9CA3@cityweb.de>
Date:	Thu, 04 Mar 1999 17:18:40 +0100
From:	Corinna Vinschen <corinna DOT vinschen AT cityweb DOT de>
X-Mailer:	Mozilla 4.04 [en] (WinNT; I)
MIME-Version:	1.0
To:	earnie_boyd AT yahoo DOT com,
	cygwin developers <cygwin-developers AT sourceware DOT cygnus DOT com>,
	"Oelke, Dan" <doelke AT opticalsolutions DOT com>
Subject:	Re: Question about making changes...
References:	<19990304143055 DOT 15593 DOT rocketmail AT send102 DOT yahoomail DOT com>

Earnie Boyd wrote:
> 
> ---Chris Faylor <cgf AT cygnus DOT com> wrote:
> >
> > The development sources are always "moving right along" and often we
> discuss
> > the changes we're making in the cygwin-developers mailing list.
> > [...]
>
> I just wanted to add for the archives sake that there are tools to
> help manage the moving target, such as CVS.  With CVS you would be
> able to know when conflicting changes were made by more than one
> person and be able to take corrective action.
> 
> I know this is off topic but; Corinna, could you explain how you're
> keeping current with snapshots?  At least there would be an entry in
> the archive for it if you do.

I'm not current with snapshots. It's in fact not easy, to keep in touch.
My normal behaviour is, to look into ChangeLog and diff of the snapshot,
to decide, if I need to be current. The decision is simple: If my changes
and the latest snapshot changes are concurrent resp. contrary or overlapping,
I have to check in the snapshots, else not.
Moreover, I'm using CVS, to keep the change history, since I decide, to
download the latest snapshot completely and to check in only _my_ latest
changes into this new snapshot, which I always do under control of CVS.

Oelke, Dan wrote:
> How do most people set up their tree's?

I have downloaded the development tree of B20.1 in early December, then
I have `./configure' in the tree's root dir. After I have done this once,
I have compiled only, what is interesting to me, especially libio, newlib
etc. Imagine a new winsup: I unpack it into the tree's root dir, cd into it
and call `./configure'. Then I have to open `Makefile' with my editor,
go to the line, which contains

	updir:= $(dir $(srcdir))

which is incorrect because of the local configure call, and change it to

	updir:= ../

I can't remember exactly, because I didn't complain any time, s.th. didn't
work instantly but AFAIK, this is one of very few interventions, I had to do.
Maybe, it's my missing insight in the process of automake/autoconf.
But nevertheless, so far, I could compile anything in the development tree.

Regards,
Corinna

- Raw text -