From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Darrington Subject: Re: Package test service for GNU maintainers Date: Tue, 19 Aug 2014 08:04:40 +0200 Message-ID: <20140819060439.GA11093@jocasta.intra> References: <87egwfjhfj.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55844) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XJcXO-0004HC-Ei for guix-devel@gnu.org; Tue, 19 Aug 2014 02:04:58 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XJcXK-0001Rz-07 for guix-devel@gnu.org; Tue, 19 Aug 2014 02:04:54 -0400 Content-Disposition: inline In-Reply-To: <87egwfjhfj.fsf@gnu.org> 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Ludovic Court??s Cc: Guix-devel On Sun, Aug 17, 2014 at 04:53:52PM +0200, Ludovic Court??s wrote: Hello! As a part of a discussion about ???cool features for GNU maintainers??? at the GHM, someone (Andreas, IIRC) suggested having a service (possibly a Web service) that would allow maintainers to upload their (pre)release tarballs and then get some feedback: ??? If the package is not available in the distro, it would just say ???sorry, your package is not available in the distro, but you can help!???. Something like that. ;-) ??? If the package is available, it would do something equivalent to ???guix build foo --with-source=foo.tar.gz??? and eventually return the build result. Upon success, it could also return a generated patch that can be sent to guix-devel for inclusion. It could also use something similar to ???guix refresh --list-dependent??? to try building dependent packages, or at least tell the maintainer to check them. I think we have most of the tools to do that, and it may be a good way to entice GNU maintainers into contributing to Guix. Since it???s a lightweight process, we could suggest to make it a recommendation in the maintainer???s guide. Thoughts? Who want to give it a go? :-) I could give it a go. However there are a couple of things which are of concern. 1. The way you describe it above, would it not be considered SaaS ? 2. By default, guix does not check that out-of-source builds are functional. "make distcheck" on the other-hand does. Do we want to duplicate the function of "make distcheck"? Perhaps we do, since I have recently seen a rather bad GNU release where it obviously wasn't run. 3. Should we check too that a package behaves sanely when cross-compiling? 4. Some years ago, somebody knocked up a similar "GNU package linter" and ran it on all GNU packages. One maintainer got very shitty about a "deficiency" that was detected - started demanding an apology, blah, blah blah ... J' -- PGP Public key ID: 1024D/2DE827B3 fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 See http://sks-keyservers.net or any PGP keyserver for public key.