OpenSSH_4.3p1 configure patch

[Corinna Vinschen]

On Feb  6 11:30, Damien Miller wrote:
> On Sat, 4 Feb 2006, Corinna Vinschen wrote:
> > > In this case, anyone who tested a snapshot from Jan 1st onwards would
> > > have been able to see the bug. Unfortunately our regress tests don't test
> > > for the problems that this bug caused, and I (incorrectly) assumed that
> > > the snapshots were receiving wider testing.
> > 
> > Honestly, you can't expect that every snapshot is tested just so,
> > without further announcement.  

You simply dismissed everything else what I said and just let this single
sentence in your reply, which looks like I'm just too lazy to take my
responsibilities as platform maintainer serious.
OpenSSH is not the only project, and besides developing Cygwin, I'm also
maintaining 30+ packages in the Cygwin distro.  And, as I mentioned, I
*am* testing from CVS once in a while.

> It would be excessive to expect anyone to test every snapshot, but I
> would hope that active distributors of OpenSSH test at least one
> snapshot per month. 
> 
> We don't operate a branched development model - CVS HEAD is supposed to
> always be stable enough to release. This means that people on this list
> should be able to stay up with -current (*) on non-production hosts (e.g.
> workstations) and not expect breakage.

I'm really wondering what's the problem to advertise changes made to
OpenSSH which you would like to be tested.  Do you want feedback or not?
We want feedback on changes made to Cygwin, consequentially we advertise
snapshots on a regular basis to get feedback as soon as possible.  This
is no guarantee to get all bugs fixed before a release, but if we don't
do this, the bugs would be certainly more, and more serious.  What's the
problem of writing a short note, "Hey guys, we added subspace
communication support, please test if that works on your platform"?


Corinna

-- 
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat