Date: Sat, 16 Oct 2004 11:30:48 +0900 From: Makoto Matsushita <matusita@jp.FreeBSD.org> To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, 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: <20041016113048M.matusita@jp.FreeBSD.org> In-Reply-To: <20041013195615.GC90229@dragon.nuxi.com> References: <20041002044957.GA36384@dragon.nuxi.com> <20041003004611E.matusita@jp.FreeBSD.org> <20041013195615.GC90229@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
obrien> There is some debate about if compat libs should be placed in
obrien> /usr/lib/compat or /usr/local/lib/compat. I'm not sure what way I fall
obrien> on this... but I'd love to know if we have consensus among committers.
IMHO it depends on where compat libraries come from. If it comes from
a part of distribution, /usr/lib/compat is good, and if it comes from
ports (or packages), ${LOCALDIR}/lib/compat would be better.
Since 6-current have no /usr/src/lib/compat, ${LOCALDIR}/lib/compat is
enough for me.
Speaking about 'compat libs,' how do we supply older libraries that is
in /lib? Make a directory /lib/compat (or whereever in /), or ...?
-- -
Makoto `MAR' Matsushita
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041016113048M.matusita>