unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: [SCM] guix source archive branch, master, updated. v0.1-234-g0206513
Date: Thu, 07 Mar 2013 14:55:16 +0100	[thread overview]
Message-ID: <87fw07e2m3.fsf@gnu.org> (raw)
In-Reply-To: <87boaw5agn.fsf@karetnikov.org> (Nikita Karetnikov's message of "Thu, 07 Mar 2013 04:18:16 +0400")

Nikita Karetnikov <nikita@karetnikov.org> skribis:

>> Such changes should be done in ‘core-updates’, not ‘master’, because
>> they entail a full rebuild.
>
> Oh, I'm sorry.  But could you explain why?  I'm puzzled because the
> commit doesn't remove anything.

guix/build/utils.scm is used by every build script; same for
gnu/build/gnu-build-system.scm.  So if you change something there,
everything has to be rebuilt.

The purpose of ‘core-updates’ is to have a staging area for changes that
require full rebuilds, so that users don’t end up rebuild everything
every other day.  ;-)

> Could you provide a list of files that shouldn't be changed in 'master'?
> I guess that 'gnu/packages/base.scm', 'gnu/packages/make-bootstrap.scm',
> and 'guix/build' shouldn't be touched.  Anything else?

make-bootstrap.scm can actually be changed at will.  base.scm can be
changed too, as long as the derivations it defines remain unchanged (for
instance, you can add comments, change ‘hello’, but not glibc.)

If in doubt, try ‘guix build coreutils -n’ after making your change to
see if it entails a full rebuild.

Ludo’.

      parent reply	other threads:[~2013-03-07 13:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1UDLYG-0004ar-JJ@vcs.savannah.gnu.org>
2013-03-06 23:45 ` [SCM] guix source archive branch, master, updated. v0.1-234-g0206513 Ludovic Courtès
2013-03-07  0:18   ` Nikita Karetnikov
2013-03-07  0:33     ` Nikita Karetnikov
2013-03-07 13:55     ` 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=87fw07e2m3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=bug-guix@gnu.org \
    --cc=nikita@karetnikov.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).