Date: Tue, 23 Mar 2010 09:47:49 -0500 From: Paul Schmehl <pschmehl_lists@tx.rr.com> To: glarkin@FreeBSD.org, freebsd-questions@freebsd.org Cc: Paul Schmehl <pschmehl_lists@tx.rr.com>, "corky1951@comcast.net >> Charlie Kester" <corky1951@comcast.net> Subject: Re: Elegant way to hack port source Message-ID: <83BEEB5783CC06E1C802658D@utd65257.utdallas.edu> In-Reply-To: <4BA40295.4090006@FreeBSD.org> References: <a14066a01003190935t4bbef41esc44c60a5b00e6144@mail.gmail.com> <20100319170159.GB71392@slackbox.erewhon.net> <20100319200130.GE265@comcast.net> <3D386E86A152519AA850205C@utd65257.utdallas.edu> <a14066a01003191404u56fd3f71mbfacff83839b7a2c@mail.gmail.com> <8B123BA51B43B4AAC86E0F3C@utd65257.utdallas.edu> <20100319220126.GH265@comcast.net> <2C40431FF3AE42C7B0234A97@utd65257.utdallas.edu> <20100319222143.GI265@comcast.net> <4BA40295.4090006@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--On Friday, March 19, 2010 19:02:45 -0400 Greg Larkin <glarkin@FreeBSD.org> wrote: > > Here's something else that I've found really useful as a port creator, > maintainer and troubleshooter. If I want to make some additional > changes to a source file that is patched by a file stored in > files/patch-...., I'll do this: > > make patch # extracts source and patches files > cd work/foobar/... ># Now make additional edits in patched file, leaving the ># .orig file alone > cd ../back/to/port/directory > make makepatch > > The makepatch target recurses through the work/foobar directory and > creates diffs for all file.ext/file.ext.orig pairs. It writes them to > the files/ directory with the patch- prefix on each so the patch target > processes them. > > The only thing to watch out for here, is that makepatch has its own file > naming convention that doesn't always mirror the port creator's. For > instance, some ports have patch files named "patch-aa", "patch-ab", etc. > The makepatch target will recreate them with filenames based on the > directory and filename of the file to be patched during the build. > > Hope that helps, Man, does it ever. Thanks for that. Which brings me to an obvious question. Where can I go to find out what all of the make targets are? Is it in /usr/ports/Mk/? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?83BEEB5783CC06E1C802658D>