From owner-cvs-src@FreeBSD.ORG Sat Oct 16 06:37:31 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA99316A4CE; Sat, 16 Oct 2004 06:37:31 +0000 (GMT) Received: from castle.jp.FreeBSD.org (castle.jp.FreeBSD.org [210.226.20.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id B6D3043D1D; Sat, 16 Oct 2004 06:37:28 +0000 (GMT) (envelope-from matusita@jp.FreeBSD.org) Received: from localhost (localhost [::1])i9G6bR883825; Sat, 16 Oct 2004 15:37:27 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <20041016061745.GA77261@dragon.nuxi.com> References: <20041013195615.GC90229@dragon.nuxi.com> <20041016113048M.matusita@jp.FreeBSD.org> <20041016061745.GA77261@dragon.nuxi.com> X-User-Agent: Mew/1.94.2 Emacs/21.3 X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20040704(IM147) Lines: 32 From: Makoto Matsushita To: obrien@FreeBSD.org Date: Sat, 16 Oct 2004 15:37:25 +0900 Message-Id: <20041016153725S.matusita@jp.FreeBSD.org> cc: cvs-src@FreeBSD.org cc: src-committers@FreeBSD.org cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/compat/compat4x.alpha libc.so.4.bz2.uu libc_r.so.4.bz2.uu libhistory.so.4.bz2.uu libm.so.2.bz2.uu libopie.so.2.bz2.uu libpcap.so.2.bz2.uu libperl.so.3.bz2.uu libreadline.so.4.bz2.uu X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Oct 2004 06:37:31 -0000 obrien> Since the compat libs from a port can also be installed on 5.x obrien> do we still want to not install them in /usr/lib/compat? Also obrien> what about machines that started out life as 5-CURRENT and are obrien> now 6-CURRENT? Hmm... maybe the first one can be handled with ports: - Assume that there's a RELENG_5 box, installed 'compat3x' distribution. - If ports/misc/compat3x is installed, remove the same libraries in /usr/lib/compat. and the second one is, em, would be hard to solve with only ports (and I don't get such situation until you mentioned, thank you). *** obrien> I don't see why they should go in the / partition. If you obrien> built a new .so (say .so.1 -> .so.2), then you should also obrien> have all the /[s]bin consumers of the .so lib updated [to use obrien> .so.2] also. (deleted following sentences) Maybe it's ok with /{s,}bin and other binaries those come from ports, but how about user-made custom binaries for their system backups or host administration related tools? They also live somewhere in /. As we can easily comes "Since they also have a source, just recompile them all" solution, but I'm afraid that that's not ok... -- - Makoto `MAR' Matsushita