More has been recently pushed to the wip-deploy2 branch. If you want to talk to me about your ideas, reach out to me as dustyweb in #guix on irc.freenode.net!
On my Mac laptop obviously there is no Guix. On my GNU laptop, guix pull takes a whole day. Haven't updated it for months. And now that I'm actively working on Nix stuff, that puts Guix even more in the background.
Once I get #racket2nix working for real (but it's already a minimally useful thing!), I will look at making a guix import racket though. That will have to be in a VM on the Mac, unless I went and got myself a more powerful GNU by then.
One thing that I want to see more of in the future is what e.g. #rust is doing:
Find the things that depend on your thing -- in their case every single crate published -- and treat them all as integration tests for your API.
#nix and #guix make this easier. I just discovered the brilliant #nox tool, where you can do `nox-review wip` on e.g. a bumped dependency and build and test every dependee.
Imagine if every project did this before releasing their point release! (and at the same time imagine that the dependees have decent tests, of course, otherwise you're just detecting whether you broke API signatures, and that's trivial to do without looking at any code except your own)
@benis @jeff That one was probably from #oggcastplanet, possibly #lobsters, probably not but not entirely impossibly #picolisp. Otherwise I'm on the GS Offtopic, Lounge, Cryptid and Tech/Programming heldscalla matrix channels, #squatconf, #heropunch, #guix, #pump.io and #scuttlebutt. That's more than enough to keep me busy.
I think you are not interested to hear which Swedish-speaking Suckerberg groups I'm on.
@taiz tfw you're on #nix or #guix so you never truly installed those things and they just go away in the next gc, instead of you having to disentangle what the things were and what things they pulled in with them.
@cwebber @azure Provisionally my ideal is #guix / #nix that is also used for intra-package dependencies, so that the daemon becomes a fine-grained compiler cache, and also that the system is modified to be able to produce non-store-y binaries for general consumption.
- Installer iso (GuixSD) (previously only USB image) - Friendlier and more helpful guix package (informs early about installed size, ambiguities etc.) - Networked guix-daemon!
Are you aware that the packaging and isolation system you are describing is almost exactly https://gnu.org/s/guix/ and https://nixos.org/nix/ and that they have 13 years of history thinking about and solving adjacent problems?
As I mess about with this, I get the impulse to look at what else is in my wiki, apart from the start page. I know there's a #guix intend-to-package page in there, but I discovered I also wrote something on #SFC, #SFLC and #debian 18 months ago, which apparently I never posted anywhere! That's the only page in the wiki apart from the start page and the guix page.
That I would discover that post right now, how's that for #synchronicity?
NOTE: History had Debian go with the Conservancy interpretation rather than the Law Center interpretation, and not shipping ZFS in the kernel.