Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 8 May 1999 13:09:36 -0600 (MDT)
From:      "Kenneth D. Merry" <ken@plutotech.com>
To:        eivind@FreeBSD.org (Eivind Eklund)
Cc:        cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sbin/camcontrol camcontrol.8 camcontrol.c src/sys/cam cam_ccb.h cam_sim.c cam_sim.h cam_xpt.c src/sys/cam/sc
Message-ID:  <199905081909.NAA64618@panzer.plutotech.com>
In-Reply-To: <19990508122349.L76212@bitbox.follo.net> from Eivind Eklund at "May 8, 1999 12:23:49 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
Eivind Eklund wrote...
> On Fri, May 07, 1999 at 09:58:57AM -0600, Kenneth D. Merry wrote:
> > Eivind Eklund wrote...
> > > On Thu, May 06, 1999 at 05:43:48PM -0700, Kenneth Merry wrote:
> > > > ken         1999/05/06 17:43:48 PDT
> > > > 
> > > >   Modified files:        (Branch: RELENG_3)
> > > [...]
> > > >   NOTE:  These changes will require recompilation of any userland
> > > >   applications, like cdrecord, xmcd, etc., that use the CAM passthrough
> > > >   interface.  A make world is recommended.
> > > 
> > > I thought we were not supposed to do this sort of thing to -stable.
> > > 
> > > Requirement for 'make world' has been tolerated (barely), but this is
> > > the first time I've seen anything requiring re-compilation of ports...
> > 
> > This wasn't done without thought -- there was a reason.  There were some
> > bug fixes that went in that required breaking binary compatibility.  I
> > didn't really make that clear in the checkin message, so here's a rundown
> > of some of the things that were broken.
> 
> [...]
> 
> > I would prefer to fix bugs in -stable rather than let them sit there and
> > annoy people or cause problems.
> 
> I wasn't saying that it wasn't the right decision - I was just
> registering surprise.
> 
> I think it would be appropriate to send a message to -announce, and it
> definately needs to go into the release notes for 3.2.  Breaking
> binary compatibility in -stable is supposed to be an event.

I don't think it's a big enough event to bother people on -announce.  If
people are running -stable, they should read the -stable list.  I sent mail
there, so those folks should be informed of the situation.

And this isn't the only thing that'll break binary compatibility in
3.2.  I fixed some problems in the devstat code back in February (just
after 3.1 went out, I think) that will also break ports that use the
devstat code.

I think people should probably expect some interfaces to be broken between
releases, since a completely stagnant userland<->kernel interface for
everything would probably indicate a dead branch.

It might be worth mentioning this stuff in the release notes, though.

Ken
-- 
Kenneth Merry
ken@plutotech.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905081909.NAA64618>