Date: Tue, 18 Jul 2017 16:22:17 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: github repo to port connection Message-ID: <02836954-770a-45ac-529e-006172a2fef8@freebsd.org> In-Reply-To: <CABT9mj8MOK9OAAU022kvqox7DFLBko7piLYMDL7snmmcD56KnA@mail.gmail.com> References: <CABT9mj9-CD96NAAPf5QEog4c1pd5r6hMbjgaG_cVun7z=bGXyw@mail.gmail.com> <20170718135446.GJ39925@home.opsec.eu> <20170718135602.GK39925@home.opsec.eu> <CABT9mj8Y=%2BWM8RwUL7UXAgO9X9hK_-qkjjXOrEomXQcssk0Fcw@mail.gmail.com> <20170718140600.GL39925@home.opsec.eu> <CABT9mj8MOK9OAAU022kvqox7DFLBko7piLYMDL7snmmcD56KnA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --B3RjmKHxXFBLET8d9J5EelaIMtGiBmd6e Content-Type: multipart/mixed; boundary="tkEbXDLQku5VIkSm2hO4nkf6s7rM13IOo"; protected-headers="v1" From: Matthew Seaman <matthew@freebsd.org> To: freebsd-ports@freebsd.org Message-ID: <02836954-770a-45ac-529e-006172a2fef8@freebsd.org> Subject: Re: github repo to port connection References: <CABT9mj9-CD96NAAPf5QEog4c1pd5r6hMbjgaG_cVun7z=bGXyw@mail.gmail.com> <20170718135446.GJ39925@home.opsec.eu> <20170718135602.GK39925@home.opsec.eu> <CABT9mj8Y=+WM8RwUL7UXAgO9X9hK_-qkjjXOrEomXQcssk0Fcw@mail.gmail.com> <20170718140600.GL39925@home.opsec.eu> <CABT9mj8MOK9OAAU022kvqox7DFLBko7piLYMDL7snmmcD56KnA@mail.gmail.com> In-Reply-To: <CABT9mj8MOK9OAAU022kvqox7DFLBko7piLYMDL7snmmcD56KnA@mail.gmail.com> --tkEbXDLQku5VIkSm2hO4nkf6s7rM13IOo Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 07/18/17 15:11, Athanasios Douitsis wrote: > Indeed, so instead of constructing the .shar, it is customary for the > maintainer to point the ports committer to the repo. Excellent. >=20 > Many many thanks, that helps a lot. >=20 Uh... the way this generally works is: To create a brand new port, raise a PR and attach a .shar file to it. It is also permissible nowadays to send in a diff. To update an existing port to a new version, raise a PR and attach a diff to it. For updating an existing port, it's always a diff. The best way to generate a diff is to check the ports tree out of SVN, then edit the port in question in-place without trying to commit any changes -- remember to 'svn add file' or 'svn rm file' if you're adding or removing entire files. Then you can generate the diff easily by 'svn diff' Fo routine maintenance of a simple port of something from GitHub, it is usually a matter of updating PORTVERSION, running 'make makesum' to pull down the new distfile and update distinfo, then running some test builds and fixing up any local patches (if needed) or updating the pkg-plist (again, only if needed). Cheers, Matthew --tkEbXDLQku5VIkSm2hO4nkf6s7rM13IOo-- --B3RjmKHxXFBLET8d9J5EelaIMtGiBmd6e Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEGfFU7L8RLlBUTj8wAFE/EOCp5OcFAlluJ6kACgkQAFE/EOCp 5OeKABAAp4FfZjytVwpIN9DTmo1CJXEq/OfR1JTjXbDlmkYi63kDiOoXRHosFmjT xSgZR7IKProUfx2jOobgG0GTL75PVg85Og3XblIaIIHCG2yh4w7NwBtzzw4rtTDI l72vOmupgFp7qpDN9YBYxSOXh4HqPYE5y/oFy5oSrS9mWUCbbLOraRhaM8SqH6L1 9Mfp+wcK16mIPSjdy0LEwOzV2Lci57XBKelYbABts1WehYLqaX1rE91hnmigpjdU VHGmjRwF+u9oeVNyK4BHbwI6MF5d0i8R2q7/TWkTu+PMNPPIujq18jhLFcqgztFp +NXFF4GYa4AKzRVSSznSOOnp+Tcbn3u+NEBQ/LFfRb1BlHvUXezrWkZqv4v6zt+j kLY0sSOZ0rvW0kE0kO7Vmb6c/hOLwk0ulefJ/rz/JmETofRFMNDMjvVkkmRR3Rc9 QsGf9sVzHSe5KngxHMI9tj5TdgfqSBz3ZTBm+lI0U+uiU/4dzrouGpWr9e4cZfci 402NJzw2Qr/IaxTLmSKa41l7rdYpgT++RS8L9TUDyMzxfv61C/7fSHnDGCZ2gnXT QFjhG/DPPmsB2CXBz4z4n+PTrg7VQTDuH1sovyz+jlQWTiduYBkpJvGTtY19ntod 5bxO83zuKtswHzuXRRWMs19FYcjYTQruJJgYf2u0PHiTV399Ngo= =/bPW -----END PGP SIGNATURE----- --B3RjmKHxXFBLET8d9J5EelaIMtGiBmd6e--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?02836954-770a-45ac-529e-006172a2fef8>