From owner-freebsd-ports@FreeBSD.ORG Tue Aug 5 01:32:25 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2535537B401 for ; Tue, 5 Aug 2003 01:32:25 -0700 (PDT) Received: from genua.rfc-networks.ie (genua.rfc-networks.ie [62.77.182.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58D7E43FE0 for ; Tue, 5 Aug 2003 01:32:24 -0700 (PDT) (envelope-from philip.reynolds@rfc-networks.ie) Received: from tear.domain (unknown [10.0.1.254]) by genua.rfc-networks.ie (Postfix) with ESMTP id 3E489548C4 for ; Tue, 5 Aug 2003 09:32:23 +0100 (IST) Received: by tear.domain (Postfix, from userid 1000) id 4BC2421150; Tue, 5 Aug 2003 08:32:23 +0000 (GMT) Date: Tue, 5 Aug 2003 08:32:23 +0000 From: Philip Reynolds To: freebsd-ports@freebsd.org Message-ID: <20030805083223.GE84015@rfc-networks.ie> References: <3F2E1EAA.5030200@ant.uni-bremen.de> <20030804170956.GA76322@mail.it.ca> <3F2F608D.9070806@ant.uni-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F2F608D.9070806@ant.uni-bremen.de> X-Operating-System: FreeBSD 4.7-STABLE X-URL: http://www.rfc-networks.ie Subject: Re: How to apply private patches to port? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: philip.reynolds@rfc-networks.ie List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Aug 2003 08:32:25 -0000 Heinrich Rebehn 65 lines of wisdom included: > Hi Paul, > > In the meantime i found the "Porter's Handbook" and also had a > look into /usr/ports/Mk/bsd.port.mk, which contains a description > of all the make targets (fetch, extract, patch ..). I wish every > Makefile would have a 'help' target, which woukd list all the > available targets. But that's only wishful thinking.. > > As for 'widespread appeal' of my patch: I guess not. It's only a > private hack for imap-uw, which is very poorly configurable. At > first, i installed it directly from source (w/o port). But now i > wanted to install the package 'imp' from the ports which depends > on imap-uw and when i issued 'make' for imp, it began to pull in > imap-uw, because it was not 'installed'(via ports) and threatened > to overwrite my private imap-uw with an unpatched version. That's > why i had the idea of expanding the imap-uw port (and also > client-2002) with my own patch. I think FORCE_PKG_REGISTER and NO_DEPENDS can help you here. The other option is to compile up the uw-imap port (it really shouldn't take that long to do a basic compilation of a port when options are being hardcoded) and use the ports system naturally and keep a local copy of your ports. -- Philip Reynolds | RFC Networks Ltd. philip.reynolds@rfc-networks.ie | +353 (0)1 8832063 http://people.rfc-networks.ie/~phil | www.rfc-networks.ie