From owner-freebsd-questions@FreeBSD.ORG Sun Jun 27 16:34:43 2004 Return-Path: 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 C8E4316A4CE for ; Sun, 27 Jun 2004 16:34:43 +0000 (GMT) Received: from out008.verizon.net (out008pub.verizon.net [206.46.170.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14FCE43D1D for ; Sun, 27 Jun 2004 16:34:43 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] ([68.161.84.3]) by out008.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040627163426.JMDL27801.out008.verizon.net@[192.168.1.3]>; Sun, 27 Jun 2004 11:34:26 -0500 Message-ID: <40DEF6FF.9030703@mac.com> Date: Sun, 27 Jun 2004 12:34:07 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040608 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kai Grossjohann References: <40D33478.3060705@vo.lu> <86n02qm2q3.fsf@rumba.de.uu.net> In-Reply-To: <86n02qm2q3.fsf@rumba.de.uu.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out008.verizon.net from [68.161.84.3] at Sun, 27 Jun 2004 11:34:26 -0500 cc: freebsd-questions@freebsd.org Subject: Re: any use to build from source? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jun 2004 16:34:43 -0000 Kai Grossjohann wrote: > Charles Swiger writes: >> Oh, yes. The first time you run into a problem and fix it yourself, >> or make a change to the programs to add some feature that you want, >> you will discover the serious advantages. >> >> However, if you never try to fix bugs or write code for yourself, then >> you aren't going to gain nearly as much from using source compared >> with using precompiled binaries. > > How does one deal with local changes in the software when installing > as a port? One way is to put your local changes into files/patch-aa [1] using diff format. Other times it's as simple as defining some environment variables by passing them into make, via /etc/make.conf, etc. -- -Chuck [1]: Choose whatever name seems appropriate, perhaps files/patch-src-file.c; the patch-aa naming convention works fine but is depricated.