unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Robert Vollmert <rob@vllmrt.net>
Cc: 36511@debbugs.gnu.org
Subject: bug#36511: extraneous recompiles of scm files while editing gnu/packages/
Date: Fri, 12 Jul 2019 22:50:24 +0200	[thread overview]
Message-ID: <87blxzdlkf.fsf@gnu.org> (raw)
In-Reply-To: <8C9B4ABA-AFF8-4CE7-A401-01B329134D03@vllmrt.net> (Robert Vollmert's message of "Fri, 12 Jul 2019 09:38:18 +0200")

Hi,

Robert Vollmert <rob@vllmrt.net> skribis:

> The suggestion was that the default workflow should be to compile the
> scheme files using `make`. That does avoid the recompile spam, but:
>
> - adding a scheme file requires going through
>   1. edit Makefile.am
>   2. call bootstrap
>   3. call configure, remembering the mystery localstatedir argument
>   4. call make, waiting through documentation and nix-daemon compiles

You only have to type ‘make’, nothing more.  ‘bootstrap’ and ‘configure’
only need to be invoked the first time.

> - I get random mysterious documentation builds throughout. E.g. just now:

I think ‘make’ is behaving as expected here, I don’t see anything
mysterious here.

> Let me know if these should be considered separate bugs worth filing.

Yeah, I think we should try to keep issues focused.  The issues you
reported are all important, but we need to boil them down to specific
problems we can address.

Thank you,
Ludo’.

      reply	other threads:[~2019-07-12 20:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05 14:22 bug#36511: extraneous recompiles of scm files while editing gnu/packages/ Robert Vollmert
2019-07-05 20:40 ` Ludovic Courtès
2019-07-08  7:50   ` Robert Vollmert
2019-07-08 10:03     ` Ludovic Courtès
2019-07-08 11:46       ` Robert Vollmert
2019-07-08 22:15         ` Ludovic Courtès
2019-07-09 15:45           ` Robert Vollmert
2019-07-12  7:40             ` Robert Vollmert
2019-07-13  8:33               ` Ludovic Courtès
2019-07-12  7:38           ` Robert Vollmert
2019-07-12 20:50             ` 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

  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=87blxzdlkf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=36511@debbugs.gnu.org \
    --cc=rob@vllmrt.net \
    /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).