From owner-freebsd-current Mon Feb 12 17:32:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 0421E37B491 for ; Mon, 12 Feb 2001 17:32:19 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f1D1VrW33790; Mon, 12 Feb 2001 18:31:53 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102130131.f1D1VrW33790@harmony.village.org> To: Peter Wemm Subject: Re: Patch for FILE problems (was Re: -CURRENT is bad for me...) Cc: Dag-Erling Smorgrav , Daniel Eischen , John Indra , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 12 Feb 2001 17:20:51 PST." <200102130120.f1D1KpU56194@mobile.wemm.org> References: <200102130120.f1D1KpU56194@mobile.wemm.org> Date: Mon, 12 Feb 2001 18:31:53 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200102130120.f1D1KpU56194@mobile.wemm.org> Peter Wemm writes: : If we had taken -current to 500, we could go to 501, 502, etc as : required to stop killing our developers, and prior to entering 5.0-BETA we : go back to the next sequentially available major number (be it 5, or 6 : if RELENG_4 bumps again). I've had problems in the past going backwards on major versions of shared libaries. The major problem is that if I have binaries that refer to libc.so.503, then when the major number is reverted back to 5, it is a nop because ld will use libc.so.503 for new binaries. What's wrong with shipping with say libc.so.505 in 5.0 and then say libc.so.645 in 6.0? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message