all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <john@darrington.wattle.id.au>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Package test service for GNU maintainers
Date: Tue, 19 Aug 2014 23:07:09 +0200	[thread overview]
Message-ID: <87wqa49ojm.fsf@gnu.org> (raw)
In-Reply-To: <20140819060439.GA11093@jocasta.intra> (John Darrington's message of "Tue, 19 Aug 2014 08:04:40 +0200")

John Darrington <john@darrington.wattle.id.au> skribis:

> I could give it a go.

Cool!

> 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.

That’s not the goal here.  The goal would just be to make sure that the
package can be integrated in the distro.

> 3. Should we check too that a package behaves sanely when cross-compiling?

Perhaps, yes.

> 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 ...

Was it the CI service at hydra.nixos.org that Rob Vermaas and I got
started?  :-)

I think here we’re aiming for something much more focused, which is
integration of (pre)releases in the distro.

Ludo’.

      parent reply	other threads:[~2014-08-20  8:45 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
2014-08-19 12:25   ` Jason Self
2014-08-19 21:07   ` Ludovic Courtès [this message]

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=87wqa49ojm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=john@darrington.wattle.id.au \
    /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.