<iyzsong>isn't the usb image enough in most case? the only one I can think of is to deploy to some VPS (which may just support ISO.)
<dmbaturin>Well, it's technically enough, but unless you have a procedure for it already, it's quite a headache. Booting from an ISO is one option/click in all hypervisors, but a disk image is something you have to make first. :)
<dmbaturin>Not that making a qcow2/vmdk/whatever is a big problem, but it's going to deter casual users from trying it IMHO.
<dmbaturin>Also, I like predefined build system macros.
<dmbaturin>Also, out of curiosity, what are real mips64el machines? I've only seen Cavium MIPS64, and it's big endian.
<iyzsong>I once have a little loongson2f notebook, but it's too slow for me :-(
<dmbaturin>And why there's no MIPS32, which is far more common than MIPS64?
<dmbaturin>I wanted to buy one of those loongson machines, but couldn't find a supplier, so I've never even seen a non-embedded MIPS myself.
<iyzsong>well, I get disappointed by loongson, won't recommend it
<dmbaturin>Got an asus x200ca (non-touchscreen one), which is pretty much blob-free, except wireless. And its UEFI has no restricted boot or other genetic diseases. But that's offtopic.
<iyzsong>the build 'macros' is 'edo' from ebuilds? we have build systems written in scheme, but reley on the package's build system to do the right thing mostly (IMO).
<dmbaturin>Also, why there is no easy fallback to hand-coded build sequences, as in (build '("./funky-setup-script.sh" "FOO=bar make" "make install")) ?
<dmbaturin>I hate packages like that (when there clearly were better options), but if the language is not well supported by autotools, or language-specific build system doesn't fit into the ./configure && make & make install model, things often get tricky.
<iyzsong>yes, then the packager have to figure it out.
<dmbaturin>Well, I mean why doing those things is so complex?
<lvlnd>Is there any way as a user to skip the testing phase? I found when I tried to install some programs while using the installation medium that building tar would fail in the test phase, and I don't really need it working 100% for temporarily installed software.
<taylanub>I also seem to be getting e.g. "substitute: warning: failed to install locale: Invalid argument" (not sure where else) even though I have glibc-locales installed and LOCPATH set. I have LANG=C and LC_CTYPE=en_US.UTF-8
*davexunit prepares to install guixsd on his laptop
<civodul>re portability, one thing i'd like is to be able to generate a USB image that has all i need, including a writable partition for $HOME
<civodul>so i could travel with it rather and use it on somebody else's laptop
<cehteh>since some years i am thinking of some p2p filesystem for this cases, things get locally cached, one can define which machine holds which files, supporting disconnected operation and re-merging things