Gidday there,
I have my own change to suexec in apache 2.0 from ports.
What I want to know is the best way to have my patch applied each time I
compile apache, without too much effort from me?
Eg, say for the sake of example my patch is in /usr/local/src/foopatch/
How would I get the ports
On Mon, Jun 25, 2007 at 09:01:21PM +1200, Josh wrote:
Gidday there,
I have my own change to suexec in apache 2.0 from ports.
What I want to know is the best way to have my patch applied each time I
compile apache, without too much effort from me?
The best way is to get the patch
Roland Smith [EMAIL PROTECTED] writes:
Unfortunately most port update tools will delete files that are not in
the master tree.
In the cases I know of, this will only happen if the same tool had
previously known about the file. So just make sure you don't use a
filename that was ever in the
to run something else.
Grant Peel wrote:
Curious, what does the patch do?
- Original Message -
From: [1]Josh
To: [EMAIL PROTECTED]
Sent: Monday, June 25, 2007 5:01 AM
Subject: Permanent apache patch
Gidday there,
I have my own change to suexec in apache
This seems to be the case... with csup at least... I would imagine
portsnap might bust it though.
Thanks :)
Lowell Gilbert wrote:
Roland Smith [1][EMAIL PROTECTED] writes:
Unfortunately most port update tools will delete files that are not in
the master tree.
In the cases I know
