On Mon, 23 Sep 2002, Mike Barcroft wrote:
> walt <[EMAIL PROTECTED]> writes:
> > May I ask a naïve question, please? World has been broken at libncurses for
> > three days. There have been dozens of commits to the -CURRENT tree during that
> > same three days.
> >
> > How do you committers to -CURRENT keep working when userland is broken? How
> > can you judge the impact of all your changes when you are not rebuilding
> > the system every day?
>
> I'm sure most of us aren't installing world each day, only building
> and installing certain things, or only building everything with an
> older world.
>
I have 2 machines..
one I commit from and one that is purely updated from a mirror of the
cvs tree.
After I've build everything relevent and often a whole world, on my
editing machine, I commit but it's still possible to make mistakes,
For example leving out part of an edit set.
Then I wait for it to cycle back to me though the mirror system
and then I do a make -k buildworld on the other machine. Hopefully
this machine represents "joe developer", and doesn't have teh missing
stuff already on it.
I go through the log and check for failures.
If I consider that that failure isn't anything to do with me, I
leave it for whoever made the mistake.
If it's my fault (e.g. this morning I failed to commit a pair of edits)
I'll catch it and fix it..
cycle time is usually a about 2 hours but sometimes a bit more.
(e.g. if you drift off to sleep before it gets back to you :-)
The key is the -k together with logging the output. Sometimes I diff
consequtive outputs.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
