Date: Sun, 24 Aug 2014 04:42:42 +0200 From: Polytropon <freebsd@edvax.de> To: "William A. Mahaffey III" <wam@hiwaay.net> Cc: freebsd-questions@FreeBSD.org Subject: Re: More pkg issues .... Message-ID: <20140824044242.6bbc8140.freebsd@edvax.de> In-Reply-To: <53F8AD3C.4060704@hiwaay.net> References: <53F766ED.5010005@hiwaay.net> <53F84FA7.5010704@FreeBSD.org> <53F87F71.7050806@hiwaay.net> <53F8822F.8030808@FreeBSD.org> <53F884BB.5080607@hiwaay.net> <53F89E3B.9080900@FreeBSD.org> <53F8AD3C.4060704@hiwaay.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 23 Aug 2014 10:03:24 -0500, William A. Mahaffey III wrote: > agreed, /usr/bin/enscript, for example .... Which looks wrong. Applications installed via ports or packages are usually installed in the /usr/local/ subtree, in this example, /usr/local/bin/enscript for the binary. All other places (like /usr/bin) are for OS provided files. There are few cases where a port can replace an OS part (e. g., CUPS can overwrite system's lpr commands, bash can be installed as /bin/bash, even statically linked). > still seems like it should > allow the install to proceed, or at least either prompt & proceed, or > have a CL option to allow the install to proceed .... There is probably a -f (force) switch, but you should know what you're doing when you use such kind of options. Things can go wrong beyond repair (in ultra-worst case, of course). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140824044242.6bbc8140.freebsd>