unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Medium-term road map
Date: Mon, 4 May 2020 12:32:02 +0200	[thread overview]
Message-ID: <CAJ3okZ01hRQiH4VO2QDAYV-SvUkstCe8SV3C3REMaPm9WZi7_A@mail.gmail.com> (raw)
In-Reply-To: <87a72oye7d.fsf@gnu.org>

Dear,

On Sun, 3 May 2020 at 22:07, Ludovic Courtès <ludo@gnu.org> wrote:

> We could write a program to build a database locally (I very much like
> the idea of “substitutes” viewed as an optimization compared to local
> computation) but that would be expensive, although it could be
> incremental.

I agree that the "substitutes" mechanism seems the right approach.
Because it allow the user to build the something locally (if they do
not trust the server or use Guix for another set packages etc.).

However, the "issue" with substitutes when pulling is that they are
rarely available.  Because Guix moves faster than the build-farm
builds; I mean my laptop is building locally -- more more than often
-- guix-manual, guix-cli, guix-extra, guix-cli-modules,
guix-extra-modules, guix-packages-base, etc. and some expensive ones ,
e.g., guix-system.


> I suppose we could reuse relevant bits of the Data Service as a library.
>
> Hmm thinking about it, by building the package-cache derivation of each
> Guix revision, one already gets a lot of information, and that is
> substitutable.  Food for thought!

Yes.  What I have in mind is: substitute a big index once and then
update it locally (incrementally, similarly as 'news' does).
The questions are:
  what does that? pull or explicit command or something else?
  how to deal with channels?


All the best,
simon


  reply	other threads:[~2020-05-04 10:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-25 13:37 Medium-term road map Ludovic Courtès
2020-04-25 16:23 ` Pierre Neidhardt
2020-05-03 20:13   ` Ludovic Courtès
2020-04-25 21:38 ` Jack Hill
2020-04-26  1:22   ` Josh Marshall
2020-05-03 20:18   ` Ludovic Courtès
2020-05-06 17:03   ` [EXT] " Thompson, David
2020-05-06 18:58     ` Efraim Flashner
2020-05-06 19:46     ` Jack Hill
2020-05-07 12:24       ` [EXT] " Thompson, David
2020-04-26 16:06 ` zimoun
2020-04-26 18:20   ` Christopher Baines
2020-05-03 20:07     ` Ludovic Courtès
2020-05-04 10:32       ` zimoun [this message]
2020-04-26 18:14 ` Christopher Baines
2020-05-03 20:11   ` Ludovic Courtès
2020-04-27  8:16 ` Andy Wingo
2020-04-27 13:06   ` Christopher Lemmer Webber
2020-04-30 21:27   ` Joshua Branson
2020-05-05 23:50 ` raingloom

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=CAJ3okZ01hRQiH4VO2QDAYV-SvUkstCe8SV3C3REMaPm9WZi7_A@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --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).