From mboxrd@z Thu Jan 1 00:00:00 1970 From: Danny Milosavljevic Subject: Re: Automated linting before master branch commit Date: Mon, 25 Mar 2019 18:24:12 +0100 Message-ID: <20190325182412.40b822db@scratchpost.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/tI3sirehTxrwU=n+LGP1w82"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:51562) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h8TL7-0005uU-2a for guix-devel@gnu.org; Mon, 25 Mar 2019 13:24:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h8TL5-0002bl-F1 for guix-devel@gnu.org; Mon, 25 Mar 2019 13:24:49 -0400 Received: from dd26836.kasserver.com ([85.13.145.193]:57170) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h8TKz-0002RK-Mt for guix-devel@gnu.org; Mon, 25 Mar 2019 13:24:43 -0400 In-Reply-To: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: mikadoZero Cc: Guix-devel --Sig_/tI3sirehTxrwU=n+LGP1w82 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi, > What do people think about automating package linting? This would be to > make sure a package is linted before it is committed to the Guix > repository master branch? A linter by its nature will in some cases flag things which are not wrong, otherwise one could just check the stuff while compiling in the first place. > I am not familiar with what Guix uses for continuous integration / > deployment. We can manually make cuirass and/or Hydra evaluate custom branches--but it's not automated. Christopher Baines is working on making patch review better--see thread "Patchwork + automated checking and testing of patches". > Estimated number of packages with autogenerated tarball: >=20 > 389 Yeah, those should be updated. With that many packages, writing a script to do it would be less annoying. --Sig_/tI3sirehTxrwU=n+LGP1w82 Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAlyZDrwACgkQ5xo1VCww uqWwtAf/WVF8fHqOPEtuRrD0JRcg2MSgAT+FoaHzzGMCh8hHem2CIunlvbsGKGUC tIWhlbfTOFR0wVTfrOkB0QtD6ZNI8gv/t/EX/tCbuJ49Ikvm6yKy0PghmDOuYKAl ALBszVTiKz89NhEvH37T5yKdW65RJ3LJo06U417DDhyzlc7erAMWxK5KboQWqC3f NXHxeh2yQIJyeSCEAzh2J7/8zJTqgQFkRGvEyTvZViq0ZqP6l4axFzBW7unXWsjo p6uWdQjpnYFX/1Yx/JMM02mDeeHkQ6gGFBMN+rf48fjLjg8a/iudPyZ7XZbn9Qew Euulgf/np6QnEhBeNkGOA6riwsFGeg== =kHyF -----END PGP SIGNATURE----- --Sig_/tI3sirehTxrwU=n+LGP1w82--