Date: Fri, 4 Jun 1999 13:36:32 -0400 (EDT) From: Matt Behrens <matt@zigg.com> To: Narvi <narvi@haldjas.folklore.ee> Cc: Roger Marquis <marquis@roble.com>, security@FreeBSD.ORG Subject: Re: SSH2 (in FreeBSD-Questions) Message-ID: <Pine.BSF.4.10.9906041325550.22269-100000@megaweapon.zigg.com> In-Reply-To: <Pine.BSF.3.96.990604194334.3570M-100000@haldjas.folklore.ee>
next in thread | previous in thread | raw e-mail | index | archive | help
[ Followups to -ports. ] On Fri, 4 Jun 1999, Narvi wrote: : Ever tried changing the PREFIX? : : make PREFIX=/usr/local/ssh all install : : Should most probably do the trick. Yep. Works on maybe half the ports. Some override PREFIX themselves; some have commands with /usr/local hardcoded in; some packages even ignore configure command-line switches to change their paths, preferring /usr/local. : > Another thing ports don't do is tell you where they install files. : > "make -n install" or "make -n real-install" rarely yields any useful : > information. Even the post-install info in /var/db/pkg lacks detail, : > especially when compared with Solaris' /var/sadm. : That is what you have the PLIST for. The PLIST that comes out of ports is usually a pretty poor representation of what is actually installed. For fun sometime, you should try installing a lot of ports then uninstalling them. Check out what's left over in /usr/local (ignoring, of course, the locale directories and other things created by the ports system itself rather than the individual ports.) I can understand how difficult it would be to actually determine what a port did install, especially since different configurations can even generate different file manifests. I don't fault the ports people -- throwing everything into a single directory structure like they come preconfigured to do is difficult to work with and track. (Actually, I really have great respect for what the ports people do. Please, don't miscontrue me, anyone.) :-) Matt Behrens <matt@zigg.com> Owner/Administrator, zigg.com Chief Engineer, Nameless IRC Network To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9906041325550.22269-100000>