Date: Sun, 29 Sep 2024 17:55:55 +0200 From: Norbert Grundmann <ngrundmann@gmx.de> To: FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: Using --recursive in Makefile / github clone Message-ID: <97c091de-889d-439c-9a61-a329c3ae58bd@gmx.de> In-Reply-To: <Zvl3wOFekkidH70p@fuz.su> References: <f9d46a4d-7735-4952-8b88-87021f172b5b@gmx.de> <Zvl1j8IV4jfMFNtm@fuz.su> <8011bacc-1e59-491a-95e7-042ae6ce162f@gmx.de> <Zvl3wOFekkidH70p@fuz.su>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks Daniel and Robert, then I must go the recommended way :-) On 9/29/24 17:52, Robert Clausecker wrote: > Hi Norbert, > > Am Sun, Sep 29, 2024 at 05:46:16PM +0200 schrieb Norbert Grundmann: >> Hi Robert, >> >> Thanks :-)=C2=A0 But is it good and recommended to use an explicit >> >> git clone --recursive repo >> >> instead of GH_TUPLE?=C2=A0 It would make things more easy... > This is not permitted. We require that distfiles be fetched in the fetc= h > phase, then be checked against the distinfo file, and only then be > extracted. git-clone(1) does not permit us to do so and can thus not be > used to obtain project source. If you submit a patch with this sort of > stuff in the Makefile, it'll be rejected. > >> Cheers, Norebrt > Yours, > Robert Clausecker > =2D- I love penguins at the south pole, windows in my house and apples on my tr= ee, but not in my computer :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?97c091de-889d-439c-9a61-a329c3ae58bd>