Date: Fri, 19 Mar 2010 13:01:01 -0400 From: Alejandro Imass <ait@p2ee.org> To: freebsd-questions@freebsd.org Subject: Re: Elegant way to hack port source Message-ID: <a14066a01003191001h46b83a01w2cb0a80bf7a075bb@mail.gmail.com> In-Reply-To: <20100319165607.GH45355@eggman.experts-exchange.com> References: <a14066a01003190935t4bbef41esc44c60a5b00e6144@mail.gmail.com> <20100319165607.GH45355@eggman.experts-exchange.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 19, 2010 at 12:56 PM, Jason <jhelfman@e-e.com> wrote: > You can do it this way in the ports system: > > http://www.freebsd.org/doc/en/books/porters-handbook/slow-patch.html > > I handle all my patching for ports this way. Ok. I guess I'll stop my laziness and RT-W-FM! Thanks! Alejandro Imass > > -jgh > > On Fri, Mar 19, 2010 at 12:35:30PM -0400, Alejandro Imass thus spake: >> >> Hi, >> >> I need to modify a file from a port before building. Specifically, the >> sane-backends pnm.c driver has a bug and the folks at the original >> project has not fixed for a while. I need to modify pnm.c in the work >> directory before compiling. What is an elegant way of doing this? If I >> make and then modify, the main make file does not see the change made >> in the file and will not recompile. And since there is no actual >> makefile in the work subdirectory I can't compile there either! >> >> There must be a FreeBSD way of dealing with modifying a port source >> before compiling. Please advise. >> >> Thanks in advance, >> Alejandro Imass >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a14066a01003191001h46b83a01w2cb0a80bf7a075bb>