From: Tanguy LE CARROUR <tanguy@bioneland.org>
To: pjotr.public12@thebird.nl
Cc: guix-devel@gnu.org
Subject: Re: GNU Hurd at Guix days
Date: Tue, 06 Feb 2024 09:33:15 +0100 [thread overview]
Message-ID: <170720839508.31230.13670003693550344730@bioneland.org> (raw)
In-Reply-To: <20240206074856.djihq2oudugzti2v@mailx.thebird.nl>
Hi Pjotr,
Quoting pjotr.public12@thebird.nl (2024-02-06 08:48:56)
> We had a very interesting discussion about the Hurd.
Very interesting, indeed! 10+ persons in a room talking about Hurd!
I guess that hadn’t happened in a long time! 😉
On my side, I decided to start patching broken packages… again! [1]
[1]: https://www.gnu.org/software//hurd/user/tlecarrour.html
First thing yesterday morning, I set up a ChildHurd and try to offload
build to it and… it worked! 😎
Unfortunately, the default image seems to be to small to build "real"
packages. I increased it, but… then my real disk was suddenly too small!
This is a problem that came up multiple times while discussing with
Simon… so I decided to upgrade my disk… and I now have to re-install
—I miserably failed my attempt at cross-installing and ended up with a
brick! 😱—, so I thought "why not use the latest installer?" [2].
[2]: https://lists.gnu.org/archive/html/guix-devel/2024-02/msg00068.html
I also have to figure out what’s the proper way to hack with this set up.
Probably a mixture of `build --system`, `build --source`, `diff -purN`,
`--with-patch=`…
So, I guess, you’ll hear from me soon! 😁
Regards,
--
Tanguy
next prev parent reply other threads:[~2024-02-06 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 7:48 GNU Hurd at Guix days pjotr.public12
2024-02-06 8:33 ` Tanguy LE CARROUR [this message]
2024-02-07 3:37 ` Maxim Cournoyer
2024-02-09 7:27 ` Guix Hurd at… Guix@Paris! [Was: GNU Hurd at Guix days] Tanguy LE CARROUR
2024-02-10 12:16 ` Hurd download image is too small; Was: " Pjotr Prins
2024-02-10 17:39 ` Tanguy LE CARROUR
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=170720839508.31230.13670003693550344730@bioneland.org \
--to=tanguy@bioneland.org \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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.