unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: guix-science@gnu.org, Peter Polidoro <peter@polidoro.io>
Subject: Re: Guix for Embedded, Hardware, Documentation, and Data
Date: Fri, 10 Dec 2021 17:18:43 -0500	[thread overview]
Message-ID: <3CA44F2F-4430-425A-A652-62AE07339A52@lepiller.eu> (raw)
In-Reply-To: <867dcceguz.fsf@polidoro.io>

[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]

I think guix can be used for more than just packages. When you say documentation, what comes to mind is package documentation, but we also have man-pages, which contains no programs, only… well… man pages :). We also have sicp that contains only a book.

With cross-compilation, it shouldn't be too hard to build something for an embedded system, though that's still something that needg to be demonstrated I think.

Le 10 décembre 2021 08:00:23 GMT-05:00, Peter Polidoro <peter@polidoro.io> a écrit :
>Could Guix be used for packages that do not strictly contain 
>operating system software?
>
>For example, could Guix be used for packages of embedded code and 
>their dependencies to be run on a little RTOS, like Zephyr, or 
>bare metal, like Arduino or PlatformIO libraries?
>
>Could it be used for hardware, like a Kicad pcb package that 
>depends on component and footprint packages, or packages of 
>FreeCAD mechanical assemblies that depend on part packages?
>
>Can Guix packages be used for documentation and other data?
>
>Or are all of these types of packages way outside the scope of 
>Guix? Although it could still be used for the operating system 
>software development environments for these types of projects, it 
>might be very powerful to package other types of code and data as 
>well.
>

[-- Attachment #2: Type: text/html, Size: 1620 bytes --]

  reply	other threads:[~2021-12-10 22:19 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 [this message]
2021-12-12  8:43   ` Efraim Flashner
2021-12-12  9:43 ` [Spam:]Guix " Konrad Hinsen
2021-12-13 13:20   ` Guix " Peter Polidoro
2021-12-13 14:48     ` [Spam:]Re: " 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=3CA44F2F-4430-425A-A652-62AE07339A52@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-science@gnu.org \
    --cc=peter@polidoro.io \
    /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).