all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Josh Marshall <joshua.r.marshall.1991@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Can general compute and packaging be more formally merged into a single case?
Date: Tue, 3 Dec 2019 19:16:23 -0500	[thread overview]
Message-ID: <CAFkJGRfwjru8USCD_S3P7oVMjq1G1-m5kEGOO0O02CSh_=2K5w@mail.gmail.com> (raw)
In-Reply-To: <CAJ3okZ2Qawh02Y++16ykp6MOUnzdXxV6pjCiyD9E9ULoA1QQhQ@mail.gmail.com>

Neat!  I'll go digging and see what I can find.

On Tue, Dec 3, 2019, 16:22 zimoun <zimon.toutoune@gmail.com> wrote:

> Hi Josh
>
> On Tue, 3 Dec 2019 at 18:34, Josh Marshall
> <joshua.r.marshall.1991@gmail.com> wrote:
> >
> > At the airport, thinking on the fundamental differences between gwl and
> > guix.  It seems like these can be articulated as the same case when
> > considering a tracked and linked compute history.
>
> On gwl-devel@gnu.org, from my understanding, we are discussing that
> and it seems related to the Content Addressable Store (CAS).
>
> Otherwise, about the differences between GWL and Guix, you can dig in
> some archeology; especially read the initial proposal by Roel and the
> comments by Ludo. (I think I already pointed to you where the related
> messages live.)
>
> > How I see this, when packaging you take checksums off of inputs not for
> > your own assurance that they are correct (though you could) but to ensure
> > that under different circumstances another user can be sure that they
> have
> > the right starting points.  Then as a matter of storing results and
> > ensuring the integrity of our results for later we take more checksums.
> > What we can do is to create a unit computational step of sorts whereby a
> > user enters a monitored shell whereby they install packages, perform
> their
> > work, and produce changes which can be taken to be outputs.
>
> This already works in GWL. :-)
>
> >All downloads,
> > uploads, and files changes tracked.
>
> To me, it is not clear how GWL should track this because they can be
> really huge.
>
> > Then perform a basic minimization
> > algorithm to reduce the inputs so long as the outputs do not differ.
>
> Which kind of minimization algorithm do you have in mind?
>
> > This
> > optimized unit computational step can then be tracked with the input
> > checksums and outputs.  This merges general compute and packaging, then
> > adding compute power only needs to scale here.
> >
> > From these, computational chains may also be produced to know a full
> graph
> > of what is happening.  Thoughts?
>
> It is already the case. If I understand well.
>
>
> All the best,
> simon
>

  reply	other threads:[~2019-12-04  0:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 16:27 Can general compute and packaging be more formally merged into a single case? Josh Marshall
2019-12-03 21:21 ` zimoun
2019-12-04  0:16   ` Josh Marshall [this message]
2019-12-06 15:31     ` Josh Marshall

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

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

  git send-email \
    --in-reply-to='CAFkJGRfwjru8USCD_S3P7oVMjq1G1-m5kEGOO0O02CSh_=2K5w@mail.gmail.com' \
    --to=joshua.r.marshall.1991@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.