From owner-freebsd-questions@FreeBSD.ORG Fri Sep 9 21:47:37 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F14216A41F for ; Fri, 9 Sep 2005 21:47:37 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from lakecmmtao05.coxmail.com (lakecmmtao05.coxmail.com [68.99.120.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9073943D45 for ; Fri, 9 Sep 2005 21:47:36 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by lakecmmtao05.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20050909214737.HTCB2425.lakecmmtao05.coxmail.com@dns1>; Fri, 9 Sep 2005 17:47:37 -0400 From: Vizion To: Kevin Kinsey Date: Fri, 9 Sep 2005 14:43:19 -0700 User-Agent: KMail/1.8 References: <200509090959.40296.vizion@vizion.occoxmail.com> <200509091146.11136.vizion@vizion.occoxmail.com> <4321FCD2.7070702@daleco.biz> In-Reply-To: <4321FCD2.7070702@daleco.biz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509091443.19853.vizion@vizion.occoxmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: php compile options X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2005 21:47:37 -0000 On Friday 09 September 2005 14:21, the author Kevin Kinsey contributed to the dialogue on- Re: php compile options: >Vizion wrote: >>On Friday 09 September 2005 11:13, the author Kevin Kinsey contributed to >> the dialogue on- >> >> Re: php compile options: >>>Vizion wrote: >> >>I do wish thiss kind of info was documented, for every port in >>Port_Install.readme or something similar- I have spent ages trying to get >> to bottom of how to deal with this! > >AFAIK, it is documented; see ports(7). > >>Different ports require different knowledge as to how they should be >>installed! > >`cd /usr/ports/category/fooport && sudo make install clean` >works in the general case for every port in the tree* (assuming >in this exact case, that you've already installed and configured >"sudo", and the directory /usr/ports/category/fooport exists and >contains a port skelton, of course). Not quite true in this case you need to know to install extensions when all the written php manuals tell you to install php and declare options. It might have been helpful to have had a Port_Install. readme file with that simple info in it - just for idiots like me!! The idiots motto should be to encourage othwers to support one in the notion: "You''ll not walk alone" david >Otherwise do it as root without >calling sudo. The system does the work, and, in the general sense, >no particular expertise is required. > >>Ah well -- live and learn I gues -- but once someone has learnt can we not >>have a siomple means of passing the learning on without wasting the time of >>every learner!! > >Ah, yes. "I am Locutus of Borg. You will be assimilated. Resistance is >futile." >But it only works that way in Star Trek ;-) Real Life is more like Will >Rogers: >"There are two ways of getting smarter. One is reading, and the other is >hanging around with smarter people." > >Between 'RTFM' and hanging around this list, I'm doing both :-D > >Kevin Kinsey > >* Occasionally a port is marked as "broken". Occasionally one is broken, >and nobody else knows about it --- yet. Both cases would be exceptions. -- 40 yrs navigating and computing in blue waters. English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after completing engineroom refit.