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: help-guix@gnu.org
Subject: Can general compute and packaging be more formally merged into a single case?
Date: Tue, 3 Dec 2019 11:27:28 -0500	[thread overview]
Message-ID: <CAFkJGRf2Bx5VMkYW4Ao9tyPfRnj-Lyv7jZxdY8RnFz1A7_0+EQ@mail.gmail.com> (raw)

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.

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.  All downloads,
uploads, and files changes tracked.  Then perform a basic minimization
algorithm to reduce the inputs so long as the outputs do not differ.  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?

             reply	other threads:[~2019-12-03 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 16:27 Josh Marshall [this message]
2019-12-03 21:21 ` Can general compute and packaging be more formally merged into a single case? zimoun
2019-12-04  0:16   ` Josh Marshall
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=CAFkJGRf2Bx5VMkYW4Ao9tyPfRnj-Lyv7jZxdY8RnFz1A7_0+EQ@mail.gmail.com \
    --to=joshua.r.marshall.1991@gmail.com \
    --cc=help-guix@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 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.