Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 08 Nov 2002 14:17:55 -0800
From:      Terry Lambert <tlambert2@mindspring.com>
To:        Andrew Kenneth Milton <akm@theinternet.com.au>
Cc:        Steve Kargl <sgk@troutmask.apl.washington.edu>, Daniel Eischen <eischen@pcnet1.pcnet.com>, "M. Warner Losh" <imp@bsdimp.com>, ataraxia@cox.net, current@FreeBSD.ORG
Subject:   Re: [PATCH] note the __sF change in src/UPDATING
Message-ID:  <3DCC3813.1833DD83@mindspring.com>
References:  <20021108.092732.124899267.imp@bsdimp.com> <Pine.GSO.4.10.10211081205020.27766-100000@pcnet1.pcnet.com> <20021108174915.GA71225@troutmask.apl.washington.edu> <20021108181611.GA90784@zeus.theinternet.com.au>

next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Kenneth Milton wrote:
> +-------[ Steve Kargl ]----------------------
> |
> | I agree with Dan.  Let's do it now.  My understanding is
> | that 5.0 will be an "early adopter" release and production
> | systems should run 4.7{8,9,..} until 5.1 is released.
> |
> | To accomplish the change, I think we need to do:
> |   1. Install a complete set of 4.7 shared libs in COMPAT4X.
> |      This should porivde the necessary runtime compatibility
> |      with 4.x.
> |   2. Bump all shared library on 5.0.  This will get rid of
> |      any interdependencies among the libraries and it deals
> |      with the version number problems I detailed in the thread
> |      "Ghost of __sF ..." a couple a days ago.
> |   3. Put a big fat WARNING in src/UPDATING about the problem
> |   4. Put the same WARNING in /etc/motd, so people currently
> |      run -current will know to update their ports.
> |   5. Broadcast the WARNING to appropriate mailing lists and
> |      newsgroups.
> 
> 6. Assume Crash Position.

7. Profit!

-- Terry

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DCC3813.1833DD83>