From: John Darrington <john@darrington.wattle.id.au>
To: Ludovic Court??s <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Package test service for GNU maintainers
Date: Tue, 19 Aug 2014 08:04:40 +0200 [thread overview]
Message-ID: <20140819060439.GA11093@jocasta.intra> (raw)
In-Reply-To: <87egwfjhfj.fsf@gnu.org>
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.
next prev parent reply other threads:[~2014-08-19 6:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 14:53 Package test service for GNU maintainers Ludovic Courtès
2014-08-18 21:46 ` Jason Self
2014-08-19 21:04 ` Ludovic Courtès
2014-08-19 6:04 ` John Darrington [this message]
2014-08-19 12:25 ` Jason Self
2014-08-19 21:07 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140819060439.GA11093@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.