From: Maxime Devos <maximedevos@telenet.be>
To: James Hobson <James.Hobson@jotron.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Questions about Cuirass
Date: Mon, 31 Oct 2022 16:55:30 +0100 [thread overview]
Message-ID: <c0c3d995-b65b-d079-d916-16a0d4a4cc2c@telenet.be> (raw)
In-Reply-To: <E5D5693E-82F3-4A99-8C70-6C5CC6437095@jotron.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1038 bytes --]
On 30-10-2022 13:50, James Hobson wrote:
> Sorry for not getting back to you.
>
> Looks promising!
>
> I wish I could release everything under a free license. Baby steps though! I’ve managed to release a few things under LGPL since I started! That’s 100% more than before!
Sounds good.
>
> But anyway. The biggest hurdle I see is that updating in an air gapped environment doesn’t seem supported because guix’s git url is hard coded. Does this need to be the case? If not, I might see if I can find an nice way of making this more configurable
There is a default, yes, but it's not hardcoded, you can override it.
Have a look at "Invoking 'guix pull'" in the manual, in particular its
'--url=URL' argument.
> James
>
> [...]
I prefer no top-posting; my e-mail client, and more generally almost all
e-mail clients I think, keep a thread of previous messages. I would
prefer to not to have to scroll down to read the rest of the message
only to discover there is none.
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 --]
prev parent reply other threads:[~2022-10-31 15:55 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
2022-10-30 12:50 ` James Hobson
2022-10-31 15:55 ` Maxime Devos [this message]
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=c0c3d995-b65b-d079-d916-16a0d4a4cc2c@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).