Date: Sat, 16 Oct 2004 15:37:25 +0900 From: Makoto Matsushita <matusita@jp.FreeBSD.org> To: obrien@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 Message-ID: <20041016153725S.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041016153725S.matusita>