IRC channel logs

<ijp>psyntax is exhausting

<ijp>well, I've hit the bottom of that well, just need to climb back up again

<OrangeShark>yay, got the tests for guile-git to work and now distcheck passes :)

<OrangeShark>there was apparently a third option, automake sets the env variable $srcdir with the location of the src code so (getenv "srcdir")

<ArneBab_>OrangeShark: nice!

<ArneBab_>paroneayea: ah, yes, the GC is not exposed yet (it’s a future feature: http://webassembly.org/docs/gc/ )

<ArneBab_>ijp: WebAssembly has a gc, but it does not expose it to client code right now.

<ArneBab_>paroneayea: I also get hit regularly by forgetting commas in Python ☺ — somehow they feel so superfluous now …

<OrangeShark>hello

<ArneBab_>hi

<dsmith-work>Happy Friday, Guilers!!

<OrangeShark>happy friday

<paroneayea>hello, *!

<paroneayea>ACTION tosses some climbing supplies to ijp

<paroneayea>stay hydrated! :)

<paroneayea>well I guess you said you were climbing out of a well, so maybe hydration is not the problem

<paroneayea>;)

<amz3>o/

<amz3>ArneBab_: any news from the word count challenge?

<OrangeShark>hey amz3

<OrangeShark>guile-git's `make distcheck` should now pass

<amz3>OrangeShark: :D

<amz3>I am curious what magic is this

<OrangeShark>there was a 3rd option, the env variable $srcdir is set by make

<amz3>yes?

<OrangeShark>it is mentioned in automake docs

<amz3>hmm

<OrangeShark>so just do (getenv "srcdir")

<amz3>it's lower caps?

<OrangeShark>yes

<amz3>it this usual for env vars? I was under the impression that env vars are always lower case

<OrangeShark>you mean uppercase?

<amz3>yes

<amz3>something like GUILE_LOAD_PATH

<amz3>ACTION looking at the commit

<OrangeShark>yeah, I usually see them uppercase, but there is probably some reasoning used here for lowercase.

<amz3>ok

<amz3>now, I'd like to say that I am not very very into doing a release myself

<amz3>I don't know the code well enough to get started

<amz3>and ...

<amz3>I will find something else..

<amz3>I need to think about it

<OrangeShark>We should probably move the project to an organization group before doing a release

<amz3>ah yes right

<OrangeShark>are we still fine with using guile-git as the project name?

<OrangeShark>I think you mentioned someone contacted you before about the name

<amz3>also ask mathieu and civodul what they want, but I think, civodul prefers to do a release ASAP and also do a lot of release

<amz3>OrangeShark: the name?

<amz3>maybe i was talking about mathieu because he is contributing to the guile-git project now

<amz3>he wants to replace some software called 'repo' or something

<OrangeShark>they already have guile-git as an optional dependency for guix

<amz3>that helps manage multiple repositories or something not sure what is

<OrangeShark>oh, so mathieu wants to use guile-git for this?

<amz3>at work I am dreaming of guix

<amz3> https://code.google.com/archive/p/git-repo/

<OrangeShark>ah, something they made for android

<amz3>yes

<amz3>this sound very exciting in the context multiple free software code base

<amz3>I mean, even in web dev with Django this could already be useful

<OrangeShark>yeah, usually a group of related projects

<amz3>at my last job, in a newspaper, we coded something like that to put in place the developer environment and later extend it to publish the whole stack to production

<OrangeShark>gnome would be similar

<amz3>yeah definitly

<OrangeShark>they have a bunch of git repos

<OrangeShark>at my work, we just put everything in the same repo

<amz3>me too

<amz3>I am moving to a multi repo project nowdays, it's very painful

<OrangeShark>well most of the projects are in the same repo

<amz3>well, I also download a bunch of libraries over git to always have a look at the latest developement and have the documentation handy

<OrangeShark>the project I work on right now is a separate repo but it depends on stuff in the other repo

<amz3>instead of going to google and stuff

<amz3>i prefer single repo

<amz3>even if I understood that creating repos is useless, and it's better to contribute to a single project I continue to fork my efforts in separate ways...

<OrangeShark>it used to be a single repo, but then all the code that was really maintained in the other project left this project get quickly outdated

<amz3>oh

<OrangeShark>in the other repo

<amz3>also when you release, you have to do multiple releases

<amz3>no?

<OrangeShark>yeah, we are separate releases

<OrangeShark>it gets confusing

<OrangeShark>amz3: I understand how you feel about forking your effort. I am tempted with the same. I need to refocus on guile-git and guile-commonmark

<amz3>I'd like to be able to work on my day job on guile stuff

<amz3>:')

<OrangeShark>same

<OrangeShark>:)

<OrangeShark>or at least on linux

<OrangeShark>I am stuck on windows :(

<amz3>oh

<amz3>you have a virtual machine?

<amz3>running GNU/Linux I mean?

<OrangeShark>no, we only use windows at work

<amz3>oh ok

<amz3>I use debian