unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Packaging Coq
Date: Fri, 05 Dec 2014 09:59:56 -0500	[thread overview]
Message-ID: <878uim5ehf.fsf@yeeloong.lan> (raw)
In-Reply-To: <20141205111738.GA15226@debian.bordeaux.inria.fr> (Andreas Enge's message of "Fri, 5 Dec 2014 12:17:38 +0100")

Andreas Enge <andreas@enge.fr> writes:

> On Thu, Dec 04, 2014 at 06:56:25PM -0500, Mark H Weaver wrote:
>> Andreas Enge <andreas@enge.fr> writes:
>> > Instead of this, you could use
>> >   #:make-flags '("world")
>> IMO, this is a misuse of #:make-flags.  'world' is not a make flag, it
>> is a make *target*.  The make flags are also passed to 'make' during the
>> default 'check' and 'install' phases.
>
> In that case, maybe we should add a variable 'build-target' to our build
> system.

Sounds reasonable to me, although it should be 'build-targets' since
there is often more than one.  Ditto for 'install-targets' and
'check-targets' (or 'test-targets') if we don't already have them.

On the other hand, I'm not sure that these are needed often enough to
justify these new variables.  What do others think?

     Mark

  reply	other threads:[~2014-12-05 15:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04  1:02 Packaging Coq Nikita Karetnikov
2014-12-04  9:49 ` Nikita Karetnikov
2014-12-04 10:26   ` Nikita Karetnikov
2014-12-04 10:07 ` Andreas Enge
2014-12-04 18:35   ` Ludovic Courtès
2014-12-04 23:56   ` Mark H Weaver
2014-12-05 11:17     ` Andreas Enge
2014-12-05 14:59       ` Mark H Weaver [this message]
2014-12-05 15:52         ` Andreas Enge
2014-12-05 19:03         ` Ludovic Courtès
2014-12-04 10:34 ` John Darrington
2014-12-04  9:46   ` Nikita Karetnikov
2014-12-05  5:25 ` Mark H Weaver

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878uim5ehf.fsf@yeeloong.lan \
    --to=mhw@netris.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).