<civodul>OrangeShark: oops, i didn't, that fixed it :-)
<civodul>i think it'd be nice if this were done automatically or something
<civodul>otherwise you may get lots of bug reports
***E4xoi is now known as exio4
<adfeno>How do I inherit the opendht package definition and also replace the snippet in the "origin" for another one of my own?
<OrangeShark>civodul: yeah, I agree. libgit2 needs to initialize a lot of stuff before it works which is why they have these functions to initialize and also to shut it down. I think most bindings don't automatically do that
<adfeno>I mean: I want to reuse the package definition, and most parts of the origin definition, modifying only the snippet inside origin.
<civodul>wingo: so i can do "guix pack guile-next" and that gives me a 23 MiB compressed binary tarball with Guile
<davexunit>civodul: there's lots of C libraries that require initialize/terminate function calls that I'm never sure of how to handle nicely in Guile
<davexunit>on one hand, I don't really want loading a module to have such side-effects
<davexunit>especially if initialization can be parameterized.
<davexunit>on the other hand, we can see that it's error prone to ask users to do it
<civodul>davexunit: in (guix gcrypt) i call it from the top-level, which has pros and cons, i agree
<davexunit>would a special form be that way to go? (with-git (do-some-stuff))
<civodul>people may still forget to use the special form :-/
<sneek>erliphant, ng0 says: sorry I can't help you at the moment, for questions regarding hydra or cuirass you better direct the question at the guix-devel at gnu.org list
<erliphant>i am building a package that has its dependencies compiled and in the store. However, the build process seems to want to access the source of the dependency even though it is already compiled. Is this expected?
<jmd>erliphant: Well, some packages are written like that.
<erliphant>@jmd - I wrote the package definition. The only interesting thing is that the dependent package uses a file:// url
<erliphant>jmd: also the dependent package is a propagated-input. To be specific both packages are Python packages that I defined myself
<erliphant>jmd: Ignore me .. I think I worked it out. Probably just a problem between keyboard and chair. Thanks for your input.
<catonano>Trying to build a package. In "build.sh" called from the makefile there's a test looking for a ".git" folder containing a config file. If it doesn't find them it prints a message complaining that the project can be built from a git checkout only. And it quits. Like this http://paste.lisp.org/display/341129
<catonano>thing is, in thhe tar.gz there is no ".git" folder
<catonano>the right thing would be to go on their mailing list and complain that this is a bug
<catonano>the corner cutting solution could be to move to the git download