From owner-freebsd-current Thu Feb 15 0: 0:13 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 9E09037B401 for ; Thu, 15 Feb 2001 00:00:06 -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 f1F805W66462 for ; Thu, 15 Feb 2001 01:00:06 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200102150800.f1F805W66462@harmony.village.org> To: freebsd-current@freebsd.org Subject: Re: Major bumping of libFOO In-reply-to: Your message of "Wed, 14 Feb 2001 23:42:34 PST." <20010214234234.C65907@dragon.nuxi.com> References: <20010214234234.C65907@dragon.nuxi.com> <20010214232503.A65907@dragon.nuxi.com> <200102142245.f1EMjvW67558@harmony.village.org> <20010214232503.A65907@dragon.nuxi.com> <200102150732.f1F7WXW43163@harmony.village.org> Date: Thu, 15 Feb 2001 01:00:05 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010214234234.C65907@dragon.nuxi.com> "David O'Brien" writes: : I'm not happy about bumping every shared lib. Can you answer: Nor am I. : (1) does a ``make world'' will not work? Peter showed that we had no : choice with libc due to the use of the host's existing install programs. make world works. But... : (2) even if #1 works, will a 6mo. old binary (using one of these libs) : run w/o the change? Will a binary from 4.2-R run? old binaries fail w/o the bump. : If this is just to keep one from having to reintall /usr/local/, I'm not : sure that is suffient reason for the bumpage. Out bumpage of libc makes all old binaries break. all of them. : Note that if you are going to bump shlib versions, you should follow the : libc.so versioning scheme. For the first bump, I disagree, but for the next yes, that's right. However, I'm leaning away from bumping now. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message