Elegant way to hack port source
ait at p2ee.org
Fri Mar 19 21:04:18 UTC 2010
On Fri, Mar 19, 2010 at 4:18 PM, Paul Schmehl <pschmehl_lists at tx.rr.com> wrote:
> --On Friday, March 19, 2010 13:01:30 -0700 Charlie Kester
> <corky1951 at comcast.net> wrote:
>> Whenever I modify a port like this, I usually make a copy of it under
>> root's home directory and install it from there. That way, I can keep
>> my copy of the portstree in complete synch with the official one, and
>> there's no need to worry about updates quashing my changes. It also
>> provides a quick-and-dirty way to see which ports I've modified.
> To the O.P.:
> How about submiting the patch to the community so it can be added by the
> port maintainer? If it actually fixes a bug in the software you can't be
> the only one would benefit from the patch.
That was going to be my next question, but I am currently debugging to
see why this common fix I've used in Linux is not not working on FBSD.
The good news is that is blowing up in the same place, just that my
quick and dirty patch is not working here. I submitted a bug this
morning to the sane team to see what their official take is on this,
and if I get it fixed temporarily for FBSD I will be sure to contact
the port maintainer and send the patch. Is there a more formal way to
submit patches to ports? or do I just figure out who the port
maintainer is and send them patch directly?
> 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
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions