IRC channel logs
2021-10-25.log
back to list of logs
<dthompson>civodul: hey thanks! the git repo has a guix.scm file so it's pretty easy to play for guix users. not 'guix install bonnie-bee' easy, but close enough! <dthompson>^ for anyone else seeing this: I made a game in 10 days for the lisp game jam. using guile, of course! <civodul>i'll give it a go tonight instead of pretending to be productive ;-) <dthompson>the game only takes a few minutes to beat. it's not that hard for people used to this type of game, but those unfamiliar with the shoot-em-up genre may find it difficult. if you're not having fun, just press ESC and that's that. :) <dthompson>I'm just happy to have released a pretty decent free culture game. <chrislck>nice package... I presume this package will be runnable until the end of time? <dthompson>but the guix.scm makes it less prone to bitrot <civodul>dthompson: you can also add a channels.scm file to be on the safe side <chrislck>(also tried guix environment --pure -l guix.scm) <dthompson>looks like guile-sdl2 is failing. that is strange. <dthompson>would need to turn up guix verbosity to understand why <dthompson>always something wrong, despite my best efforts! <dthompson>thanks for trying. I will help debug for as long you have the energy to keep trying. <chrislck>np. may not be always timerich but can feed back regularly until it's fixed. <dthompson>chrislck: I'm sure you have better things to spend time on. but if you do try again... happy to help. :) <chrislck>np not sure how much I can offer; but if you push into your repo I'll feed back from time to time <RhodiumToad>ugh, why do library authors invent so many ways to make memory management hard <lilyp>dthompson, chrislck: with recent guix, you should be able to simply (define chickadee (@ (gnu packages game-development) chickadee)) and ignore the local definitions <manumanumanu>I haven't touched a proper computer for almost three weeks <RhodiumToad>I found what I think is a bug in the module system :-) <RhodiumToad>the cause is that define-module* processes #:re-export _before_ processing #:duplicates, which seems both wrong an (as shown) inconsistent <RhodiumToad>the fact that it behaves differently according to whether the sources were recompiled is a nice touch <RhodiumToad>I'm guessing it's an expand vs. load thing (in the sense of (eval-when)) <lilyp>welp, I cheated really hard to get a backtrace :( <dthompson>lilyp: I need to build against git checkouts since I fixed bugs in the dependencies during the jam. <dthompson>civodul: huh... I don't get that error here. I ran 'guix pull' this morning and rebuilt my environment, too. <lilyp>Uhm, you really don't need to build against a checkout of the release tho <lilyp>change a bit in the hash, it'll barf <lilyp>Guix doesn't barf if you have the thing already in store. <lilyp>You need to change the hash to make it see "oh, there's something different". <dthompson>I've been pushing new commits all week and updating the definitions <dthompson>this would have to be a very recent regression that guix introduced <civodul>dthompson: perhaps because you have it in cache? <dthompson>it's possible, but I ran 'guix pull' not that long before I started the jam. <lilyp>Try `guix gc' otherwise if you're not convinced <lilyp>Trust me, I've been bitten by this for the past two years. <civodul>yeah, you can try "guix build /gnu/store/1sfyih800f5w0qzrx0hj6gvhmk5vi712-git-checkout.drv --check" <lilyp>by my own contribution to Guix channels, including the main one <dthompson>the fact that this appears to be a non-universal issue is interesting <dthompson>I just rebuilt the environment from scratch and it all worked. <civodul>dthompson: did you try the command above? <civodul>probably you can't reproduce it because you already have the output of that derivation in store <civodul>(cd /tmp/guile-sdl2; git checkout d31c27ac48f81a534b28531e3d5fa626890be59f; guix hash -rx .) => 106pnw4ifgkrgyj84jgpz5gnbgshjcrp10wcyw1skgzqni1mrmg3 <civodul>it's a good idea to add the usual 'file-name' field because that avoids mistakes like when you update the commit ID but forget to update the content hash <civodul>anyway, not sure if that's what happened, weird! <civodul>dthompson: i just played, got to hit "x" a few times and all, much fun :-) <dthompson>civodul: thanks! first time I've made game music. very basic but works. <dthompson>I'll check for mistakes with the git checkouts but I just saw guix re-clone the repos. when I update the commit id I always edit the hash so that guix throws an error about it. then I copy/paste the actual hash it outputs.