From owner-freebsd-security Fri Jun 4 10:38: 8 1999 Delivered-To: freebsd-security@freebsd.org Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (Postfix) with ESMTP id 0BE9814D4E for ; Fri, 4 Jun 1999 10:38:04 -0700 (PDT) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.9.3/8.9.2) with ESMTP id NAA22407; Fri, 4 Jun 1999 13:36:32 -0400 (EDT) (envelope-from matt@zigg.com) Date: Fri, 4 Jun 1999 13:36:32 -0400 (EDT) From: Matt Behrens Reply-To: Matt Behrens , freebsd-ports@FreeBSD.ORG To: Narvi Cc: Roger Marquis , security@FreeBSD.ORG Subject: Re: SSH2 (in FreeBSD-Questions) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ 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 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