From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54416) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ga1VQ-0003Aj-AQ for guix-patches@gnu.org; Thu, 20 Dec 2018 11:49:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ga1VO-0000fw-CC for guix-patches@gnu.org; Thu, 20 Dec 2018 11:49:04 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:52418) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ga1VO-0000fR-6R for guix-patches@gnu.org; Thu, 20 Dec 2018 11:49:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ga1VN-00077S-Ua for guix-patches@gnu.org; Thu, 20 Dec 2018 11:49:01 -0500 Subject: [bug#33801] import: github: Support source URIs that redirect to GitHub Resent-Message-ID: From: Arun Isaac In-Reply-To: <87k1k4p3gl.fsf@gnu.org> References: <87d0pxtciz.fsf@gnu.org> <87woo4qxg7.fsf@gnu.org> <87k1k4p3gl.fsf@gnu.org> Date: Thu, 20 Dec 2018 22:18:23 +0530 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 33801@debbugs.gnu.org > We can use heuristics in many cases to determine whether an updater > applies to a package; most of the time, that=E2=80=99s only based on the = URL, > and it might also work for many cgit instances=E2=80=94those that have = =E2=80=9C/cgit=E2=80=9D > in their URL. > > Then again, I expect that a growing number of packages will be obtained > through =E2=80=98git-fetch=E2=80=99, and the updater for such a thing is = trivial > (interestingly it=E2=80=99s not yet implemented though :-)). > > So I feel like at present we don=E2=80=99t have strong evidence that that= the > simple URL-based approach would not scale. Agreed! Better to not complicate things beyond what is necessary at this point. I am not confident that good heuristics exist. But, if we do use git-fetch for the majority of our packages, like you said, updating will be trivial. I will proceed with the lint check as discussed earlier.