Date: Tue, 12 Dec 2000 08:33:34 +0100 From: Andreas Klemm <andreas@klemm.gtn.com> To: David Gilbert <dgilbert@velocet.ca> Cc: Brian Dean <bsd@bsdhome.com>, Mike Meyer <mwm@mired.org>, current@FreeBSD.ORG Subject: Re: [current] Re: Confusing error messages from shell image activation Message-ID: <20001212083334.A15613@titan.klemm.gtn.com> In-Reply-To: <14900.26674.605585.357915@trooper.velocet.net>; from dgilbert@velocet.ca on Mon, Dec 11, 2000 at 12:37:54AM -0500 References: <14898.33404.356173.963351@guru.mired.org> <14898.31393.228926.763711@guru.mired.org> <Pine.BSF.4.21.0012091347030.88984-100000@turtle.looksharp.net> <200012100904.CAA27546@harmony.village.org> <3A336781.94E1646@newsguy.com> <14899.41809.754369.259894@guru.mired.org> <200012101557.KAA29588@khavrinen.lcs.mit.edu> <14899.43958.622675.847234@guru.mired.org> <20001210120840.C38697@vger.bsdhome.com> <14900.26674.605585.357915@trooper.velocet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 11, 2000 at 12:37:54AM -0500, David Gilbert wrote:
> ... but /usr/pkg supplanting /usr/local is one of the things that I
> like about NetBSD.
/usr/pkg sounds a little bit odd ... ( at least for my ears).
Why not choose what Solaris uses (/opt) ?
It would be an advantage, when designing filesystem size of your OS,
that now you would have two completely separate paths /usr and /opt.
Installing ports in /usr means, having a too large /usr or to mount
a new filsystem under /usr (/usr/local). Mounting an fs under a mounted
fs I dislike much ...
What about the following installation hierarchy
/opt/category/port/{bin,etc,include,lib,libexec,man,sbin,...}
with symlinks to
/opt/{bin,etc,include,lib,libexec,man,sbin,...}
This would be an advantage for larger packages, as now you can very
easily see, what belongs to a package and what not.
Additionally you can install multiple versions of a port at the
same time, and slowly migrate the configs/settings to the new port.
For critical server application this scheme gives you more fine grained
control, concerning what version to use and you can easily go back if
you need...
pkg_version -c is cool, but it simply overwrites your working port,
keeps the configs, but pray, that everything runs.
The above suggested symlinks are a needed evil, so that you again only
need one place for manpages and binaries...
It gives you a lot more directories and symlinks, but when installing
it on a different filesystem, I think you can very easily live with
it, concerning the better control over installed packages.
Another plus is, that you now see _directly_, what files, config-files,
etc belong to a software, that is huge and complex ...
packages like KDE wouldn't f*up /usr/local as they do now.
Teaching KDE to install in /usr/local/kde is complex and I lost
fun doing so when I frist tried a year ago...
Andreas ///
--
Andreas Klemm Powered by FreeBSD SMP
Songs from our band >>64Bits<<............http://www.apsfilter.org/64bits.html
My homepage................................ http://people.FreeBSD.ORG/~andreas
Please note: Apsfilter got a NEW HOME................http://www.apsfilter.org/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001212083334.A15613>