Date: Sun, 25 Nov 2018 23:41:30 +0300 From: Yuri Pankov <yuripv@yuripv.net> To: "Dan Mahoney (Gushi)" <freebsd@gushi.org>, freebsd-ports@freebsd.org Subject: Re: Best way to generate a patch file Message-ID: <b1e0c74c-88ec-4b22-c623-e7e34dfef32b@yuripv.net> In-Reply-To: <alpine.BSF.2.20.1811251059540.13596@prime.gushi.org> References: <alpine.BSF.2.20.1811251059540.13596@prime.gushi.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --564dRwE3Va1w3dvo71Y0na5G42Hxnm8tl Content-Type: multipart/mixed; boundary="fWk0cgJyBsypZ9Ndm7LKIrmPTgna87onD"; protected-headers="v1" From: Yuri Pankov <yuripv@yuripv.net> To: "Dan Mahoney (Gushi)" <freebsd@gushi.org>, freebsd-ports@freebsd.org Message-ID: <b1e0c74c-88ec-4b22-c623-e7e34dfef32b@yuripv.net> Subject: Re: Best way to generate a patch file References: <alpine.BSF.2.20.1811251059540.13596@prime.gushi.org> In-Reply-To: <alpine.BSF.2.20.1811251059540.13596@prime.gushi.org> --fWk0cgJyBsypZ9Ndm7LKIrmPTgna87onD Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Dan Mahoney (Gushi) wrote: > All, >=20 > I'm requesting takeover of a couple of FreeBSD ports (cvs and dma, > although dma is now in base, I imagine the port will be used to track > upstream changes before they make it into base). >=20 > What has been requested thusfar is a diff to update maintainer.=C2=A0 S= eems > simple enough, right, effectively a one-line patch/diff? >=20 > So, how do I go about it?=C2=A0 I could certainly cd to /usr/ports/mail= /dma, > copy Makefile to Makefile.orig, and run a manual diff Makefile.orig > Makefile > /tmp/patch, while in that directory.=C2=A0 That would apply = only > for the single file, obviously. >=20 > Or I could clone the entire port, and make a unified diff.=C2=A0 Yes, m= ore > complicated and perhaps unnecessary for a one-line-in-one-file patch, > but maybe some tooling expects that (I couldn't find a good rule of > thumb here). >=20 > Finally, in googling around, I found a makefile target that's called > "make makepatch" -- which isn't documented in 'man ports', and which I > *think* is not used for tracking patches that will live the lifetime of= > a port, but there's no section in the porters handbook that covers this= =2E >=20 > That is to say, the entire "patching" section in the porter's handbook > covers "lifecycle" (./files) patches, and not "bugreport" patches: >=20 > https://www.freebsd.org/doc/en/books/porters-handbook/slow-patch.html Check https://www.freebsd.org/doc/en/books/porters-handbook/port-upgrading.html= #svn-diff. Also, I think it's general rule of thumb that you should set yourself as maintainer along with submitting actual changes to the port (upgrading, fixing, etc.). --fWk0cgJyBsypZ9Ndm7LKIrmPTgna87onD-- --564dRwE3Va1w3dvo71Y0na5G42Hxnm8tl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+Gq3PsPeLT4tL/9wk4vgf7Eq4WwFAlv7CQUACgkQk4vgf7Eq 4Wx91ggAgH5bcblLoIncONiJgHlOVM9KexLRMfpNeQhewWiKgvQhxXbS+b+OAqz2 92tEI+9IRETO5XW+ZBUnjSAPYr2LMvLQAY3E1IA6TFcJHQiwfN8I8vD0YEShZf5T FhkAJNjNNxONv6fJtczfVW1ZXh0KQgsM82GeWBTCObZIXS0koHN5z+F77TlGxPSw d5i2TzifcTcdTDqY/NG/SfRkQn5w5h1p0ht31J4MedlPno7ZNe9GWCe2fPXf7jaE t/eWP16PecCUt5L5sOvnBxN3NwSgexAxYWuFqu/H26TO1pHOKWR3Z9BMG5oABHz9 kCkZG0jnwvrZCYvEZuuk8O2H5Es2Pg== =CMBt -----END PGP SIGNATURE----- --564dRwE3Va1w3dvo71Y0na5G42Hxnm8tl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1e0c74c-88ec-4b22-c623-e7e34dfef32b>