Vincent Legoll writes:
Hello Vincent,
> I just had a tour of that branch, it looks like there are interesting
> patches wrt cross-building, aren't those ready for upstream (core-
> updates maybe) ?
Yes, some of them (gnutls, git, python) have just been cleaned-up and
applied to core-updates.
>
Hello Matthew,
LGTM, (I think I saw it myself, but forgot about it)
I think you should send your patches to:
guix-patc...@gnu.org
Thanks
--
Vincent Legoll
* doc/shepherd.texi (Jump Start): Fix typo.
---
doc/shepherd.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/shepherd.texi b/doc/shepherd.texi
index ed484c8..ecc1621 100644
--- a/doc/shepherd.texi
+++ b/doc/shepherd.texi
@@ -135,7 +135,7 @@ reference section.
Note t
Hello,
I just had a tour of that branch, it looks like there are interesting
patches wrt cross-building, aren't those ready for upstream (core-
updates maybe) ?
I'm looking at the first one (for perl) for example...
I've been trying to cross-compile the binary-tarball to new arches,
without any
On 19/04/2020 16:35, Marius Bakke wrote:
Another question, why is the VM image partitionned
like that (root first, then EFI) ? It makes root
partition resizing more painful than needed.
This one's still bugging me though
Not really an answer to your question, but you can safely delete the EFI
Hello,
I just reset wip-hurd-vm to ba6bdb0d0b gnu: guix: Run `make
update-guix-package'.
Like before, you should be able to run
./pre-inst-env guix build -f gnu/system/hurd.scm
on it to get a VM and start it doing something like
guix environment --ad-hoc qemu -- qemu-system-i386 -enab
Vincent Legoll writes:
>> Another question, why is the VM image partitionned
>> like that (root first, then EFI) ? It makes root
>> partition resizing more painful than needed.
>
> This one's still bugging me though
Not really an answer to your question, but you can safely delete the EFI
partiti
