From: Peter Polidoro <peter@polidoro.io>
To: guix-science@gnu.org
Subject: Re: Guix for Embedded, Hardware, Documentation, and Data
Date: Mon, 13 Dec 2021 08:20:53 -0500 [thread overview]
Message-ID: <86sfuwa9p3.fsf@polidoro.io> (raw)
In-Reply-To: <m135myxinz.fsf@fastmail.net>
Efraim Flashner <efraim@flashner.co.il> writes:
> I would say actually
> running Guix on any of this small hardware is outside of the
> scope of
> Guix.
Konrad Hinsen <konrad.hinsen@cnrs.fr> writes:
> Guix the software distribution: it depends. I doubt you would
> have much
> success with submitting a pull request for adding video clips,
> for
> example.
These are good points, thanks. I was not thinking of trying to run
Guix on embedded hardware without the GNU operation system,
though, or of trying to add large media files to Guix proper.
I was mostly curious about using Guix as a universal package
manager for organizing and distributing code and data, especially
for reproducible science, and I was wondering for which cases it
would not make sense to use Guix.
For example, after a researcher publishes a paper, years later
someone may want exact versions of the experimental data, analysis
software, and documentation referenced in the paper. They may also
want the exact version of the experimental rig used to collect the
data, the software, hardware, and firmware, and the exact version
of the development environments used to create each one. Guix
seems ideal for this, especially if the code and data are in text
files rather than large binaries.
The packages you all told me about, like the sicp book, give me
clues about how I might try packaging something like circuit board
files. I will give it a try, thanks!
> For a nice example of using Guix for something else than
> software, see
> this blog post:
>
> https://guix.gnu.org/en/blog/2021/reproducible-data-processing-pipelines/
The guix.gnu.org site appears to be down right now, but I look
forward to reading this when it is available again.
next prev parent reply other threads:[~2021-12-13 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 13:00 Guix for Embedded, Hardware, Documentation, and Data Peter Polidoro
2021-12-10 22:18 ` Julien Lepiller
2021-12-12 8:43 ` Efraim Flashner
2021-12-12 9:43 ` [Spam:]Guix " Konrad Hinsen
2021-12-13 13:20 ` Peter Polidoro [this message]
2021-12-13 14:48 ` [Spam:]Re: Guix " Konrad Hinsen
2021-12-14 15:19 ` Peter Polidoro
2021-12-13 14:25 ` zimoun
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=86sfuwa9p3.fsf@polidoro.io \
--to=peter@polidoro.io \
--cc=guix-science@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.
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).