From: Maxime Devos <maximedevos@telenet.be>
To: James Hobson <James.Hobson@jotron.com>,
"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Questions about Cuirass
Date: Fri, 21 Oct 2022 11:01:02 +0200 [thread overview]
Message-ID: <1573d3ab-2a17-8405-feb7-b3833f12e3ac@telenet.be> (raw)
In-Reply-To: <E47A2A82-1DFB-455F-8CF1-8613ADB42D58@jotron.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 2513 bytes --]
On 20-10-2022 23:19, James Hobson wrote:
> Hello!
>
> Currently evaluating guix for embedded systems at work. But I have a few questions that I can’t quite work out from the docs. Please feel no obligation to answer!
>
> Please note that my guix journey is at its very beginning. I’ve not even had a go at packaging!
>
> Question 1
> We would need to host the guix substitute server in an airgapped environment. The server would contain plain guix packages, our in house packages, and maybe patched guix packages. Would that be possible without having to rebuild the entire guix package set? We don’t have so many build machines, especially not for armv7.
You can tell Cuirass to only build a selection of packages (and their
dependencies), by using a manifest, then not all of Guix is compiled but
only what's necessary for your particular purpose.
Also, your Cuirass instance still needs access to the source code of the
packages somehow, which will need to be somehow be squared with your
'airgapped environment', though maybe 'copy over the result of guix
build --sources=transitive" would be acceptable (*).
(*) except that this is after application of snippet; some kind of
"--sources=raw,transitive" may be needed.
> Question 2 [...]
I don't know the answer to this.
> Question 3
> Our software is sadly proprietary. Is there a way for guix build to selectively unpack and patch all non-proprietary sources so that we can provide it to anyone who asks? I feel like if this isn’t a thing already, I guess I can write it in scheme?
I assume you meant 'patch all non-proprietary' -> 'patch out all
proprietary', such that at least the free parts can be used?
In that case, this is done already in some package definitions in Guix,
by a 'snippet' removing parts that are non-free, such that they are not
built and are not part of "guix build --source". (See: ‘Snippets versus
Phases’ in the documentation, though it doesn't mention non-free things
directly).
The Guix user can still access the unpatched source code though, by
inspecting the package definition and removing the snippet, so it looks
to me like that option is only good for 'you aren't allowed to modify
this part of the source code + guix build --source must produce
something free', not for 'you aren't allowed to see or distribute this'
situations.
Alternatively, you could avoid all this complexity by making your
software free.
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-10-21 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 21:19 Questions about Cuirass James Hobson
2022-10-21 9:01 ` Maxime Devos [this message]
2022-10-30 12:50 ` James Hobson
2022-10-31 15:55 ` Maxime Devos
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=1573d3ab-2a17-8405-feb7-b3833f12e3ac@telenet.be \
--to=maximedevos@telenet.be \
--cc=James.Hobson@jotron.com \
--cc=guix-devel@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.