unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Building the core-updates branch.
Date: Sun, 07 Feb 2021 19:22:42 +0100	[thread overview]
Message-ID: <87im734u19.fsf@gnu.org> (raw)
In-Reply-To: <878s80zx0j.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 06 Feb 2021 22:50:20 +0100")


Hey Ludo,

> Agreed, I think that was the intent.  Can we make it focus on the ‘core’
> subset?  How does one do that nowadays?  Looks like my sqlite3/Cuirass
> foo is no longer helpful.  :-)

Turns out "core-updates" is still configured to build the "core" subset,
I don't really understand why the evaluation 74281 triggered the build
of so many packages.

Regarding the sqlite3 -> psql transition, there are not that much
differences. I fire up psql this way:

--8<---------------cut here---------------start------------->8---
sudo -u cuirass -s /bin/sh -c 'psql cuirass -h /var/run/postgresql'
--8<---------------cut here---------------end--------------->8---

The commands that are listed here[1] are still (mostly) relevant, even
if this document would really need to be updated. I plan to improve the
Cuirass documentation for a future 1.0 release anyways.

Thanks,

Mathieu

[1]: https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/doc/cuirass-howto.org


  reply	other threads:[~2021-02-07 18:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06  8:06 Building the core-updates branch Mathieu Othacehe
2021-02-06 11:11 ` Mathieu Othacehe
2021-02-06 21:48   ` Ludovic Courtès
2021-02-06 22:21   ` Ricardo Wurmus
2021-02-06 13:40 ` zimoun
2021-02-06 21:50 ` Ludovic Courtès
2021-02-07 18:22   ` Mathieu Othacehe [this message]
2021-02-07 18:43     ` Mathieu Othacehe
2021-02-07 19:29       ` Leo Famulari

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=87im734u19.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --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 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).