From owner-freebsd-ports@freebsd.org Fri May 13 07:10:39 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A623B398E3 for ; Fri, 13 May 2016 07:10:39 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 609B6131F for ; Fri, 13 May 2016 07:10:39 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-225-151.lns20.per1.internode.on.net [121.45.225.151]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u4D7ASKx041158 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 13 May 2016 00:10:32 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: suggested patch for bsd.ports.mk To: "Julian H. Stacey" References: <201605121920.u4CJJwfH003932@fire.js.berklix.net> Cc: freebsd-ports@freebsd.org From: Julian Elischer Message-ID: <0ce71142-cb8e-6f85-605b-8f8ad8bc874d@freebsd.org> Date: Fri, 13 May 2016 15:10:22 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <201605121920.u4CJJwfH003932@fire.js.berklix.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 May 2016 07:10:39 -0000 On 13/05/2016 3:19 AM, Julian H. Stacey wrote: > Julian Elischer wrote: >> This patch is pretty self explanatory. >> >> it allows us to keep patches for various ports separately in a sparse >> hierarchy while not having to write to the ports tree itself. > Nice idea ! I'll have a look. > BTW I've had something somewhat similar for maybe a decade or so > http://berklix.com/~jhs/bin/.csh/customise > mine does: > - src + ports, > - generic + personal diffs as 2 parallel patch trees (cos some of my patches > I hope may appeal generaly but some probaly only I will ever want), > - targets a load of different release levels inc current > - only does a one off pass, installing files & applying diffs to a virgin > tree. > > Your approach will be nicer than mine for tracking current ports. > I look forward to trying it, & if necessary perhaps bending my patch > trees to fit your macros :-) thanks.. It works for us and allows us to slide stuff forwards, only stopping occasionally to fix a broken patch. For a "Release" we check out a snapshot of the ports tree, and branch the patches tree in case we want to change or add a patch to that snapshot of ports. anyone (in ports) think this is a BAD idea? > > >> In case the list scrubs hte text attachment (diff) here's the >> description part of the diff. > The MIME enclosure made it through mailman unscathed :-) > > Cheers, > Julian > -- > Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich http://berklix.eu/jhs/ > Mail plain text, No quoted-printable, HTML, base64, MS.doc. > Prefix old lines '> ' Reply below old, like play script. Break lines by 80. > Britain denies 700,000+ Brits in EU a vote. http://www.berklix.eu/brexit/ >