Date: Wed, 28 Apr 2004 23:26:48 +0200 From: Simon Barner <barner@in.tum.de> To: Jason Dusek <jdusek@cs.uiowa.edu> Cc: "Ports@BSD" <freebsd-ports@freebsd.org> Subject: Re: Adding Src Message-ID: <20040428212648.GC49165@zi025.glhnet.mhn.de> In-Reply-To: <40901E65.4070405@cs.uiowa.edu> References: <40901E65.4070405@cs.uiowa.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--0vzXIDBeUiKkjNJl
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Jason Dusek wrote:
> Hi Everyone,
>=20
> How do I add a file to a port? I would like to add a new component to a=
=20
> port and then use a patch to the Makefile to get everything to turn out=
=20
> all right. Is this easy or hard? Is there a hand book on how to do=20
> neat hacks on the ports?
Hi,
I see two possibilities:
1. Create a patch for the new file(s):
touch filename.c.orig
vim filename.c (hack, hack, hack)
diff -u filename.c.orig filename.c > ${FILESDIR}/patch-filename.c
2. Simply put the file into the files directory, and use the pre-patch
target (in the port Makefile)
=20
pre-patch:
${CP} ${FILESDIR}/filename.c ${WRKDIR}/right/directory
I'd say that #2 is obfuscates your extension less, so I'd prefer it.
But before you submit a PR, you should ask yourself whether the ports
collection is the right place for you extension, (i.e. is it really
FreeBSD specific), or whether it should be incorporated into the
official release.
Simon
--0vzXIDBeUiKkjNJl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFAkCGYCkn+/eutqCoRAkQWAJ4rdBMQG+Nesx3JTHKOlGnBHEU9LQCgtKB4
rZf4GvNxcAf8JWlLNAkHL3M=
=sgq9
-----END PGP SIGNATURE-----
--0vzXIDBeUiKkjNJl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040428212648.GC49165>