From owner-freebsd-ports@FreeBSD.ORG Fri Sep 7 15:11:04 2012 Return-Path: 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 A59921065697; Fri, 7 Sep 2012 15:11:04 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id D08DC8FC20; Fri, 7 Sep 2012 15:11:02 +0000 (UTC) Received: by bkcje9 with SMTP id je9so1591543bkc.13 for ; Fri, 07 Sep 2012 08:11:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=s2aLsN7Avm18sNQNo1qAikNEC37DVSISCl5U6IUP3hE=; b=dUYG/OS+hQOgLhSRV3KaL19hTv5MQ76ZRM0BHSsKwnx7Qtvxg30CmHRwgacLeeaTf2 defW7QwywleQqoi3r2kRH+TS/5cDFqrBXE1nrlGNGeB8TERM7MvJhlXR95BJ/BU9mYXe moWc9Qel8Po3L5xHnGCvOlhET2YO2OZ+PtNfupdMLyACvXuB7RiRnjjtbCAeqA3CQMBg M1YX36fijrjgJXUXCpDi3BWyq00JawfyDAmtBweg1Wa4g+UEW6S1MzSB4ZvtkafUuThX MOrxyFHZiL9NS4xAJj7/pwpTugDvSzOjxi6HsDI0RRvy42fZsKRq2xn1qtX0OcrWNKoO UuWw== MIME-Version: 1.0 Received: by 10.205.118.138 with SMTP id fq10mr3026872bkc.58.1347030661902; Fri, 07 Sep 2012 08:11:01 -0700 (PDT) Received: by 10.204.10.141 with HTTP; Fri, 7 Sep 2012 08:11:01 -0700 (PDT) Received: by 10.204.10.141 with HTTP; Fri, 7 Sep 2012 08:11:01 -0700 (PDT) In-Reply-To: <20120907163800.79026725@FreeBSD.org> References: <5049E9D2.2060209@FreeBSD.org> <5049DF41.9090607@FreeBSD.org> <20120907163800.79026725@FreeBSD.org> Date: Fri, 7 Sep 2012 16:11:01 +0100 Message-ID: From: Chris Rees To: Pawel Pekala Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Steven Hartland , Beat Gaetzi , FreeBSD Mailing List Subject: Re: [FreeBSD-Announce] Announcing the end of port CVS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Sep 2012 15:11:04 -0000 On 7 Sep 2012 15:39, "Pawel Pekala" wrote: > > Dnia 2012-09-07, o godz. 12:57:42 > "Steven Hartland" napisa=C5=82(a): > > >Is there no way to tell it not to delete unknown files so we > >don't have to add addional steps to the workflow flow of adding > >additional patches to local port builds? > > > >I appreciate things must move forward but this seems like a step > >backwards in terms of functionality :( > > I`m using portsnap for some time now and wanted to have my /usr/ports > untouched but also I have my own patches for some of the software that > I use. I have come up with not ideal but simple solution, my make.conf > contains something like this: > > .if ${.CURDIR:M/usr/ports/*} > LOCALPATCHDIR=3D /home/corn/patches > > . if exists(${LOCALPATCHDIR}/${.CURDIR:T}) > LOCAL_PATCHES!=3D find ${LOCALPATCHDIR}/${.CURDIR:T} -type f > EXTRA_PATCHES+=3D ${LOCAL_PATCHES} > . endif > .endif > > LOCALPATCHDIR contains folders with names of ports I want to patch > which hold my patches inside them. > > Be aware that this will break when you want to patch port that shares > name with some other port but different category. This situation is > rare but it could happen. > > This inconvenience could probably be easily fixed when UNIQUENAME work > will be committed to the ports tree, but I'm not sure when this will be. Well, as long as they don't collide with any files named, I'm pretty sure svn will ignore them, and even merge changes (eg to Makefiles) Chris