Date: Fri, 15 Jul 2005 09:35:19 +0200 From: Pav Lucistnik <pav@FreeBSD.org> To: Woody Carey <woodycarey@hotmail.com> Cc: doc@FreeBSD.org Subject: Re: docs/82705: [PATCH] porters handbook - 4.6 patching - add note for context l Message-ID: <1121412919.92732.2.camel@pav.hide.vol.cz> In-Reply-To: <BAY102-F124B7D60F55FC07F77C238C9D00@phx.gbl> References: <BAY102-F124B7D60F55FC07F77C238C9D00@phx.gbl>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
Woody Carey píše v čt 14. 07. 2005 v 22:10 -0700:
> Key words: "if you generate your patch from WRKDIR". To do this is not
> explicitly stated
> in the porters handbook. Maybe add it?
Section 4.4 Patching have this sentence:
All patches should be relative to WRKSRC (generally the directory your
port's tarball unpacks itself into, that being where the build is done).
That's exactly what I had on mind. Maybe I'll change "should" to "must".
> Slow Porting:
>
> Write your port makefile in stages:
> 1) write it to 'make fetch' the tarball
> 2) write the part that does the 'extract'
> 3) Now hack on it in WRKDIR and generate your diffs from their, so that your
> patches will apply cleanly. Write your 'patch' target. (or do-patch or
> $PATCH or whatever)
> 4) Now add your 'configure', 'build' and 'install' stages incrementally.
That's how every sane people do it, yes. But we're not writing How-To,
but a comprehensive Handbook which documents all possible aspect of
ports infrastructure. So this does not fit much in now.
--
Pav Lucistnik <pav@oook.cz>
<pav@FreeBSD.org>
On real UNIX, /usr/bin/more prints -More-.
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)
iD8DBQBC12c3ntdYP8FOsoIRApOVAKCQW3pV2j1Zj7+oNFqwDSUkEniykACgs4jU
MaX2DhUvLYTX8rq5R2RZEkQ=
=Ze5v
-----END PGP SIGNATURE-----
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1121412919.92732.2.camel>
