<youlysses>Has a wrapper for texinfo documents been written yet? <youlysses>civodul: Probably wrong terminology, my brain is some-what fried at this point... a system in-which a local-user can read texinfo files by default. Maybe it was just an odd/non-configured thing in NixOS, but while the packages for various bits of documentation was there, they didn't default there. <youlysses>Possibly just an info/emacs info problem too? <Arne`>If I have a file called mercurial.scm in some folder, with (define-module (mercurial) … and (define-public mercurial…, what is the exact guix call to install the mercurial package? <Arne`>guix package -e "(@ (mercurial) mercurial)" does not work… <civodul>youlysses: you need to set INFOPATH to point to ~/.guix-profile/share/info <civodul>now, the 'dir' file doesn't get updated, currently <Arne`>civodul: I adjusted the version-control.scm file and copied it to ~/ <Arne`>to experiment with building packages <civodul>can you paste the error and the file? <Arne`>I get this guix package: error: failed to evaluate expression `(@ (vcs mercurial) hg)': (wrong-type-arg "module-variable" "Wrong type argument in position ~A (expecting ~A): ~S" (1 "module" #f) (#f)) <Arne`>currently I tried this: $ guix package -e "(@ (vcs mercurial) hg)" <Arne`>guix package: error: failed to evaluate expression `(@ (vcs mercurial) hg)': (wrong-type-arg "module-variable" "Wrong type argument in position ~A (expecting ~A): ~S" (1 "module" #f) (#f)) <civodul>what does this do: guile -c '(@ (vcs mercurial) hg)' ? <Arne`>civodul: does that show what I did wrong? <civodul>Arne`: what about guile -c '(use-modules (vcs mercurial))' ? <Arne`>ERROR: In procedure scm-error: <Arne`>ERROR: no code for module (vcs mercurial) <civodul>remember that the file must be called vcs/mercurial.scm <civodul>and that 'vcs' dir must be in Guile's search path <civodul>IOW, $GUILE_LOAD_PATH must be set appropriately <Arne`>so there are already filesystem categories <Arne`>I removed the vcs prefix and call it like this: $ GUILE_LOAD_PATH=. guix package -e '(@ (mercurial) hg)' <Arne`>why is it necessary to give the (name "…") additionally to the package name in (define-public PACKAGENAME? <civodul>so the 'name' field is what the command-line tools show <civodul>whereas the variable name is, well, the variable name <civodul>often they're the same, but not always <civodul>for instance because sometimes there are several variants of a given package <Arne`>civodul: could the 'name' field be made optional? That should save 1 line for most packages… <Arne`>civodul: Is there a way to skip the strip phase in the python-build-system? <Arne`>(I get File format not recognized) <Arne`>… wait, no. That succeeded (just didn’t strip the files). <Arne`>last line: guix/serialization.scm:49:4: In procedure bv-u32-ref: Wrong type argument in position 1 (expecting bytevector): #<eof> <civodul>the "File format not recognized" is harmless <Arne`>(besides: guix pull does not work for me) <civodul>i think it'll work if you run the "guix package" a second time... <Arne`>I installed 0.3, and that’s what guix --version still reports. <civodul>could you report the bug nonetheless? <civodul>it seems to happen when installing something not built yet <civodul>i thought i had fixed it, but maybe not <Arne`>civodul: should I also file a bug-report for making the (name) optional? <civodul>because that's no really doable: package objects exist regardless of whether they're bound to a variable <Arne`>isn’t define-public a macro, which does get the variable name? <Arne`>so couldn’t it check whether there is a (name) field, and if not, just add it? <civodul>so we could have define-package, define-public-package, etc. <civodul>'define-public' boils down to 'define', and 'define' knows nothing about 'package' objects <Arne`>so this is an implementation details which (currently?) requires an explicit name? <Arne`>so I guess the wish is implementable in the infrastructure. It might not be high-priority, but it can be done at some point. <Arne`>(hopefully does not require changes deep down) <Arne`>besides: Mercurial now installed. <Arne`>You’ll get a patch for version-control.scm <Arne`>Do I need to register for that? <Arne`>(damn, forgot to note that the package is pretty rough…) <Arne`>it’s essentially just a stripped down copy of the bazaar package with a new uri… <civodul>well, as long as it's usable, that's fine <Arne`>can I remove a package from a file? Something like the inverse of -e '(@ …)' <Arne`>I like being able to swapping packages this quickly. <Arne`>why does guix pull always get the full guix-master.tar.gz snapshot? <civodul>Arne`: ideally we'd have server support to only fetch diffs (or use rsync), but we don't have that currently <civodul>that's why it pulls all of the tarball ***ae is now known as Guest29481