From owner-freebsd-ports@FreeBSD.ORG Mon Jun 4 16:11:32 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CD22816A400 for ; Mon, 4 Jun 2007 16:11:32 +0000 (UTC) (envelope-from schneecrash@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239]) by mx1.freebsd.org (Postfix) with ESMTP id 779A713C4AD for ; Mon, 4 Jun 2007 16:11:32 +0000 (UTC) (envelope-from schneecrash@gmail.com) Received: by wx-out-0506.google.com with SMTP id h28so1110855wxd for ; Mon, 04 Jun 2007 09:11:31 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=jvhP47LG9xY+hISA72rOkYk6Ef0XuHo9ayHw4Nhst8nu1B7cmPMdSn86Ql4fu9re+IWMWjTanAs2LBG3u1N1bUt3aY6bcTiG7KKZkYeQvGoKlIZTAnxlskDZ8eOot+i3/zoiYtQ4ND7QxvnMikl5sp0not0a1Ffz9GPqJT5lMS0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=TXTqewiM0HPANqWPWDdnOVVjaokedDdPnV6bbtkdl2pyIsumtfY3TQ/M4BytXq4foP1gAXtosxIw1BPPOHh7awPpTfREgOC7rN7eQhBaU65NVYMVzqi/epqBC+fx9F0u2mTHXA2tjEQRNqQwwD0qcHrhAGLc3mdUAjgh7vOOv24= Received: by 10.90.115.4 with SMTP id n4mr3820962agc.1180973491597; Mon, 04 Jun 2007 09:11:31 -0700 (PDT) Received: by 10.90.50.6 with HTTP; Mon, 4 Jun 2007 09:11:27 -0700 (PDT) Message-ID: <70f41ba20706040911m2444520cmc5b29083d6c7d76c@mail.gmail.com> Date: Mon, 4 Jun 2007 09:11:27 -0700 From: snowcrash+freebsd Sender: schneecrash@gmail.com To: "Jeffrey Goldberg" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <70f41ba20706040801t786d6409pf8687ac3f31c43ee@mail.gmail.com> X-Google-Sender-Auth: 215121d4ca8bf1e4 Cc: freebsd-ports@freebsd.org Subject: Re: exim PORT -- when to use? when to 'go manual'? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2007 16:11:32 -0000 hi, > > now, I want to "upgrade" exim on that router to add 'just' > > DNSBL-filtering on the router, and have it function as a transparent > > gateway to another lan-based, exim router. > > Does that "upgrade" involve a different version of the exim tarball > than the one used in ports, bad choice of words on my part :-/ nope. i simply mean, here, same version as ports, just "turning on" the capability(ies) as i normally do in from-src builds in Local/Makefile. thos config params are, in the port, in ITS 'Makefile' ... hence, config changes would be changing the included port files. iiuc. > or is the change that you need somewhere else? just in Makefile -- used for the COMPILE phase -- and local RUNTIME config options like ip-per-domain specification, etc etc > > do folks recommend still using the PORT install? > > It depends. heh. yup. > Make your own patch of the port and keep that some place that won't > be over written by portsnap or whatever you use to keep your ports > tree up to date. > > Then have a script that patches your port tree after you do such an > update. hm. now that you mention it, i suppose that the PORT /may/ be setup to look for upgrade-proof config files in (non?)standard locations. i'll dig-about and look ... i admit, as great (!) as PORTS are, i'm just not yet used to NOT 'doing it all' myself. > Of course you should submit your patch to the port to the port > maintainer. good point. thanks!