I was looking to package [PaperWM][1][2] today, a tiling window manager
extension for gnome-shell. To my surprise, it's an excellent candidate for
copy-build-system! So I think I will wait for this to merge first. Good job
with this!
--
Alex Griffin
[1]: https://github.com/paperwm/PaperWM
[2]:
Bengt Richter writes:
>> Why would we want to know whether a package build process has a problem
>> with that particular variable?
> Debugging unexpected results?
As fun as that is, I think we have enough things to debug already! :-)
> I was reacting to
> ┌─
On 17.02.20 18:15, Alex Sassmannshausen wrote:> This is by far the
fastest way of deploying to Hetzner VMs I've found
> yet.
>
> It also means you can use Hetzner's CLI for creating and managing your
> VMs.
>
> It's on my to do list to create a solid guix deploy server creation
> module for guix.
On 17.02.20 17:55, Ellen Papsch wrote:> a few days ago I requested the
Guix installer from Hetzner as well. I
> gave them the ISO URL from Guix website. They mounted it without
> modification, which prevented boot due to the image being compressed. I
> had to supply the uncompressed image, which bo
Hi!
Some packages are frequently without substitutes, like Racket and MAME.
Link between the two? They both take a long time to build. So I wonder
if this is not because the build somehow timeouts.
I see that there is a `timeout' property on packages like chromium,
qtwebkit, etc.
Would it make
Hello Alex,
Alex Sassmannshausen writes:
[...]
> Now I use a different approach: deploy a debian server then use a
> guix-infect style script (gleaned from the guix deploy code for digital
> ocean).
could you please share that "guix-infect" script?
I think this could/should become an entry in
Am Montag, den 17.02.2020, 18:15 +0100 schrieb Alex Sassmannshausen:
>
>
> So I deploy debian, then copy across a script and run that. This
> takes
> care of turning the debian machine into a guix machine and deploys my
> sys config immediately.
>
> This is by far the fastest way of deploying
>> > The term "nothing" is mitigated; i.e. "nothing" means: a booted system
>> > running a (linux) kernel. Right?
>> No, I mean bootstrapped from bare metal.
>> No Kernel
>> No firmware
>> No microcode
>> No Bios
>> Just individual TTL logic circuits
> Is it ready yet?
Well the parts all the way t
Hi Chris,
On Sun, 16 Feb 2020 at 10:00, Christopher Baines wrote:
> I think the first step towards this would be to experiment with fetching
> data from the Software Heritage API. Do you know how you'd fetch data
> about the output from a fixed output derivation (like harfbuzz)?
>
> http://data.
