Date: Fri, 18 Aug 2017 15:45:23 +0200 From: Mathieu Arnold <mat@FreeBSD.org> To: Alexey Dokuchaev <danfe@FreeBSD.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r448034 - head/Mk Message-ID: <7fc6a440-3ace-0552-843f-7922701525b5@FreeBSD.org> In-Reply-To: <20170818130323.GA77829@FreeBSD.org> References: <201708161250.v7GCoAZa030778@repo.freebsd.org> <20170818130323.GA77829@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --sKhv9ginSqxmpSUNcu20NfmXP9vNBblBs Content-Type: multipart/mixed; boundary="idIR5UruS2JF8jbpUNEtr4oI5ambMeplT"; protected-headers="v1" From: Mathieu Arnold <mat@FreeBSD.org> To: Alexey Dokuchaev <danfe@FreeBSD.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Message-ID: <7fc6a440-3ace-0552-843f-7922701525b5@FreeBSD.org> Subject: Re: svn commit: r448034 - head/Mk References: <201708161250.v7GCoAZa030778@repo.freebsd.org> <20170818130323.GA77829@FreeBSD.org> In-Reply-To: <20170818130323.GA77829@FreeBSD.org> --idIR5UruS2JF8jbpUNEtr4oI5ambMeplT Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: fr Le 18/08/2017 =C3=A0 15:03, Alexey Dokuchaev a =C3=A9crit=C2=A0: > On Wed, Aug 16, 2017 at 12:50:10PM +0000, Mathieu Arnold wrote: >> New Revision: 448034 >> URL: https://svnweb.freebsd.org/changeset/ports/448034 >> >> Log: >> Add a git-clone target to clone the github repositories referenced i= n >> ports using USE_GITHUB. > What is it useful for (specifically within the ports tree) that fetchin= g > specific commit hash won't provide? Cloning the repo implies that one'= s > intended to work on it and thus needs all the history. For an arbitrar= y > port that one wants to build it's an overkill. Also, how feasible is t= o > cache cloned repo (like we cache normal distfiles now)? This is an easy way for the port maintainer to get the repository to check for newer versions, patches, or running git describe on a commit hash, or whatever they want to do with the repository, without having to look at the Makefile to see what the account and projects are, and type the git clone line. It is not supposed to be used during the build process, and as such, I do not see why it would be needed to cache things. Or how caching would work. --=20 Mathieu Arnold --idIR5UruS2JF8jbpUNEtr4oI5ambMeplT-- --sKhv9ginSqxmpSUNcu20NfmXP9vNBblBs Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJZlu92XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzQUI2OTc4OUQyRUQxMjEwNjQ0MEJBNUIz QTQ1MTZGMzUxODNDRTQ4AAoJEDpFFvNRg85IFiUP/A+s63HYHAHjtiu+485HxENk kTUhAKsEn24/HvT6nhapqsU4CkEXY+702u/MZu5o1ijQMXkw//YipTEWDV7FsiJ4 iR39rru0dyd3di1HSsSk4GWB57AgvdtWDs1VBiWXxUtFUcPhxkENyQ6H1+oPIeY0 tLvo7CLcpvNbvLzMOPOrNpmWFEHlV1p4h+8mFd+OhBgIWBB5ETIVRKsmKRmhvJhz IzSRwiGMzvudD5RMZDLEOH9a8lTxwG2qbK8BWHhKR12LO5vftBIBZDPAmb2xEvTk dhc62xlA4a6n/INdksncd3q3+cR1Maf5W7CT5j2uTM+bRmB1ZqctAkaWy9/2crXP eZWM85gpv+ccGRcurGm59oSJD9nPouqlsMMhTQozfOVOsPI9KuWMnZLYbNOicwF2 KobojWflIHay5FfBy7vxsDKKSw3RjebWbNcUpKmaTFf+N8y715WhdJPGFkRNgVBi iccZXqY69pS09q/S2/PPi7CRKhz23c5BPw5ajJFUrwIqZjQocX+NdiLd3CBlrr1u AtA4X6T5r7KH3iy66lYIFnGEQ+e8NceEVvqhfrq+RhyeaoZ1t3OIX3WV/AEAa1s7 qpQrY+a8YGUwm0BkWU29DEb+K6ZnCWWFmiajeL7LeC1sSCgiC/3RhcA+EX4BEb7M ileeYuk+9U6xn3jN+NX3 =oVsV -----END PGP SIGNATURE----- --sKhv9ginSqxmpSUNcu20NfmXP9vNBblBs--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7fc6a440-3ace-0552-843f-7922701525b5>