From owner-freebsd-questions@FreeBSD.ORG Tue Mar 27 17:24:43 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9464416A474 for ; Tue, 27 Mar 2007 17:24:43 +0000 (UTC) (envelope-from beech@alaskaparadise.com) Received: from stargate.alaskaparadise.com (7-137-58-66.gci.net [66.58.137.7]) by mx1.freebsd.org (Postfix) with ESMTP id 18CBF13C4BA for ; Tue, 27 Mar 2007 17:24:41 +0000 (UTC) (envelope-from beech@alaskaparadise.com) Received: from localhost (localhost [127.0.0.1]) by stargate.alaskaparadise.com (Postfix) with ESMTP id 33DBB7DEA; Tue, 27 Mar 2007 09:24:36 -0800 (AKDT) From: Beech Rintoul Organization: FreeBSD Port Maintainer To: freebsd-questions@freebsd.org Date: Tue, 27 Mar 2007 09:24:30 -0800 User-Agent: KMail/1.9.6 References: <005d01c76fdd$e67f33a0$0400020a@mickey> <3DA7AD9F-4CCA-4BB4-8C6F-B1A8B430C28D@gmail.com> <00d301c7708e$b65ddc60$0400020a@mickey> In-Reply-To: <00d301c7708e$b65ddc60$0400020a@mickey> X-Face: jC2w\k*Q1\0DA2Q0Eh&BrP/Rt2M,^2O#R07VoT98m*>miQF9%Bi9vy`F6cPjwEe?m,)=?utf-8?q?2=0A=09X=3FM=5C=3AOE9QgZ?="xT3/n3,3MJ7N=Cfkmi%f(w^~X"SUxn>; 27NO; C+)g[7J`$G*SN>{<=?utf-8?q?O=3Bg7=7C=0A=09o=7D=265A=5D4?=@7D`=Eb@Zs1Ln814?]|k@'bG=.Ca"[|8+_.OsNAo8!#?4u MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200703270924.33559.beech@alaskaparadise.com> Cc: Don O'Neil Subject: Re: Updating Bind & OpenSSL on 6.1-Stable/Release X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: beech@alaskaparadise.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2007 17:24:43 -0000 On Tuesday 27 March 2007, Don O'Neil said: > Don't assume that just because this is the first time I've raised > concerns about the ports means that this is the first time I've > used FreeBSD.... I've been using FreeBSD since 1.X. > > My point is that it's a pain the rear to do a CVSUP/Buildworld > (takes a long time) so the ports collection is the easiest way to > update/upgrade software. > > It would be nice to have some sort of reference as to how the > original software was built and installed (the build options) or > have the ports be built to match the original to facilitate easy > upgrade of one or two items. I agree that in general these are 'add > on' tools, but there are core functions (bind, ssh, etc...) that > get patched from time to time because of security and it's a LOT > quicker to re-install the port than it is to do a buildworld. Upgrading the base ports a piece at a time is an excellent way to shoot yourself in the foot. I would install the port, put NO_BIND= true in /etc/make.conf. You can define the executable and files in /etc/rc.conf. AFAIK, most of the base ports can be set up this way. Then, they become independent of the world build and can be maintained with your favorite port tools. I use the port version of bind on my nameserver and have never had any problems with compatibility except when I built it with PORT_REPLACES_BASE_BIND9. That turned out to be a *BAD* idea. Beech > > These are just my observations. > > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org] On Behalf Of Eric > Crist Sent: Tuesday, March 27, 2007 5:10 AM > To: Don O'Neil > Cc: freebsd-questions@freebsd.org > Subject: Re: Updating Bind & OpenSSL on 6.1-Stable/Release > > On Mar 27, 2007, at 12:12 AM, Don O'Neil wrote: > > If they are 'ports' specificly built for FreeBSD, shouldn't the > > port maintainer make them install like the originals were? Makes > > sense to me.... > > > > Or maybe the original install/release needs to be changed to > > install the same as the port. > > > > It's a pain having to debug where everything went, change config > > files, update startup scripts, make symlinks, etc... When if it > > were Linux a simple RPM install would update it and I'd be done > > with it. > > > > Just my observations. > > The ports tree installs things to the /usr/local/ prefix, to help > you keep your ports and base system separate. This is a normal > behavior, and has been normal for a lot longer than you have been > using FreeBSD. I apologize, but I doubt the developers are going > to change the standard behavior just because you got confused the > first time you tried to replace a base system component. > > Look here in section 4.5.2.1: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports- > using.html > > ----- > Eric F Crist > Secure Computing Networks > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" -- --------------------------------------------------------------------------------------- Beech Rintoul - Port Maintainer - beech@alaskaparadise.com /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html ---------------------------------------------------------------------------------------