Date: Mon, 25 Jun 2007 17:53:11 +0200 From: Roland Smith <rsmith@xs4all.nl> To: Josh <bsd@kajs.co.nz> Cc: freebsd-questions@freebsd.org Subject: Re: Permanent apache patch Message-ID: <20070625155311.GA28294@slackbox.xs4all.nl> In-Reply-To: <467F8461.1080104@kajs.co.nz> References: <467F8461.1080104@kajs.co.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
--d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 25, 2007 at 09:01:21PM +1200, Josh wrote: > Gidday there, >=20 > I have my own change to suexec in apache 2.0 from ports. >=20 > What I want to know is the best way to have my patch applied each time I= =20 > compile apache, without too much effort from me? The best way is to get the patch added into the port, if the maintainer is willing. :-)=20 > Eg, say for the sake of example my patch is in /usr/local/src/foopatch/ >=20 > How would I get the ports system to apply it each time I compiled apache? Just put it in the files subdirectory under the port directory, just before you build the port. Look at other patches to see from which directory they are applied, and make yours match. Unfortunately most port update tools will delete files that are not in the master tree.=20 Roland --=20 R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFGf+TnEnfvsMMhpyURAszJAKCvfqnmeL1gyQ8F3ui5Asbw9XMuCgCcCpzQ zW5fHvt7klk1gwyYqf8IwMM= =DN7X -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070625155311.GA28294>