Date: Wed, 15 Apr 2015 08:58:18 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Kurt Jaeger <pi@FreeBSD.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r384005 - in head/www/squid: . files Message-ID: <20150415085818.GA50397@FreeBSD.org> In-Reply-To: <20150414174346.GJ1017@f10.opsec.eu> References: <201504141634.t3EGYbUI070548@svn.freebsd.org> <20150414164147.GA14599@FreeBSD.org> <20150414174346.GJ1017@f10.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 14, 2015 at 07:43:46PM +0200, Kurt Jaeger wrote: > So what is the correct way to convert a port with a bunch of files/ stuff > to the proper patch format ? Technically, simply running "make makepatch" would convert them all. However, you don't necessarily need to do this. Patches are volatile thing, they tend to come and go. So simply creating new patches with "make makepatch" (and not later overwriting it) should be enough. > Yes, I might be able to reverse engineer this mechanism, but maybe I > will miss some nuance -- so I would appreciate a short README that helps > me to convert this files into the proper syntax. There's an explanatory comment around line 1102 of b.p.m. that explains how makepatch works. ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150415085818.GA50397>