Date: Fri, 19 Mar 2010 15:21:43 -0700 From: Charlie Kester <corky1951@comcast.net> To: freebsd-questions@freebsd.org Subject: Re: Elegant way to hack port source Message-ID: <20100319222143.GI265@comcast.net> In-Reply-To: <2C40431FF3AE42C7B0234A97@utd65257.utdallas.edu> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri 19 Mar 2010 at 15:07:44 PDT Paul Schmehl wrote: >--On Friday, March 19, 2010 15:01:27 -0700 Charlie Kester ><corky1951@comcast.net> wrote: >> >>Again, no need for the separate 'make extract' step. >>In fact, I'd go straight to 'make build' or 'make install' here, and >>skip the separate 'make patch' too. >> > >Thanks, Charles. You taught me something today. :-) You're welcome. We're here to help. :) The main point I wanted to make was to run "make patch" BEFORE editing the port's sourcecode, so you don't lose the work done by the maintainer And you would lose that if you simply did "make extract" and then started hacking on the result. Or, what amounts to the same thing, if you grabbed the distfile and unzipped it into your home directory or somewhere.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100319222143.GI265>