--On Friday, March 19, 2010 19:02:45 -0400 Greg Larkin glar...@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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Schmehl wrote:
--On Friday, March 19, 2010 19:02:45 -0400 Greg Larkin
glar...@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
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
On Fri, Mar 19, 2010 at 12:05 PM, Alejandro Imass a...@p2ee.org wrote:
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
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.
-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.
On Fri, Mar 19, 2010 at 12:44 PM, Alberto Mijares amijar...@gmail.com wrote:
On Fri, Mar 19, 2010 at 12:05 PM, Alejandro Imass a...@p2ee.org wrote:
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
On Fri, Mar 19, 2010 at 12:56 PM, Jason jhelf...@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
On Fri, Mar 19, 2010 at 12:35:30PM -0400, Alejandro Imass wrote:
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
On Fri, Mar 19, 2010 at 1:01 PM, Roland Smith rsm...@xs4all.nl wrote:
On Fri, Mar 19, 2010 at 12:35:30PM -0400, Alejandro Imass wrote:
Hi,
I need to modify a file from a port before building. Specifically, the
[...]
Add the patch to the files/ directory of the port. The patch should be
On Fri 19 Mar 2010 at 10:01:59 PDT Roland Smith wrote:
On Fri, Mar 19, 2010 at 12:35:30PM -0400, Alejandro Imass wrote:
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
Charlie == Charlie Kester corky1...@comcast.net writes:
Charlie Whenever I modify a port like this, I usually make a copy of it under
Charlie root's home directory and install it from there. That way, I can keep
Charlie my copy of the portstree in complete synch with the official one, and
--On Friday, March 19, 2010 13:01:30 -0700 Charlie Kester
corky1...@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,
On Fri 19 Mar 2010 at 13:06:41 PDT Randal L. Schwartz wrote:
Charlie == Charlie Kester corky1...@comcast.net writes:
Charlie Whenever I modify a port like this, I usually make a copy of it under
Charlie root's home directory and install it from there. That way, I can keep
Charlie my copy of
On Fri, Mar 19, 2010 at 4:18 PM, Paul Schmehl pschmehl_li...@tx.rr.com wrote:
--On Friday, March 19, 2010 13:01:30 -0700 Charlie Kester
corky1...@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
--On Friday, March 19, 2010 17:04:17 -0400 Alejandro Imass a...@p2ee.org
wrote:
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
On Fri 19 Mar 2010 at 14:34:23 PDT Paul Schmehl wrote:
--On Friday, March 19, 2010 17:04:17 -0400 Alejandro Imass a...@p2ee.org
wrote:
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
--On Friday, March 19, 2010 15:01:27 -0700 Charlie Kester
corky1...@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
On Fri 19 Mar 2010 at 15:07:44 PDT Paul Schmehl wrote:
--On Friday, March 19, 2010 15:01:27 -0700 Charlie Kester
corky1...@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'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charlie Kester wrote:
On Fri 19 Mar 2010 at 15:07:44 PDT Paul Schmehl wrote:
--On Friday, March 19, 2010 15:01:27 -0700 Charlie Kester
corky1...@comcast.net wrote:
Again, no need for the separate 'make extract' step.
In fact, I'd go straight to
On Fri 19 Mar 2010 at 16:02:45 PDT Greg Larkin wrote:
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.
Now it's my
20 matches
Mail list logo
