<Apteryx>Hmm. I'm trying to make udisks build with its manpages, but this requires the docbook to be registed in the xml catalog. Do we have such a catalogue on GuixSD?
<Apteryx>I have two options from my understanding of xsltproc: 1) Iappend an entry to "/etc/xml/catalog" which points to the path (docbook-xsl), or 2) I set some env variable "SGML_CATALOG_FILES" to the path (docbook-xsl) to be used by the gnu build system, and have to hack autoconf files into calling xsltproc with the --catalogs option... The former seems simpler, right?
<marusich>Apteryx, I don't have an answer for that; the best I can do is suggest looking to see if any existing packages do something similar.
<marusich>A few recursive greps "grep -ri mykeyword ." and maybe git log searches (e.g., "git log -SSGML_CATALOG_FILES") might help
<marusich>If you mean that we cannot build the manpages for the "udisks" package unless certain state is present in the /etc/xml/catalog system file, then in the interest of making the build self-contained and reproducible, your option (2) seems preferable. I don't know much about what you're trying to do, though, so I could be mistaken.
<marusich>In addition, if to accomplish (2) you need to change the autoconf files, I wonder if perhaps that's a change you could push to get put in upstream, so that we can just specify the environment variable in the build and be done with it?
<Apteryx>marusich: I'm going to try every options by hand at first, to see what works. Thanks :)
<Apteryx>Scheme question: can I insert a (let* ) anywhere? Say, between a #:keyword-arg and its value (list ...)?
<marusich>Apteryx, since a let* form will evaluate to the value of the last expression in its body, you can use a let* form anywhere you would normally need some value.
<Apteryx>Is there a way to "step" the code as I do a "guix build"? I'm still having a error: ERROR: In procedure scm_lreadr: /gnu/store/n70dbq007rqamxmrzjrfssla5ypb4bdv-my-udisks-2.1.7-guile-builder:1:4627: Unknown # object: #\\<. The modified udisks package now looks like this with the backquoting: http://paste.lisp.org/display/330614.
<ng0>my understanding, from the limited exposure with gogs and gitlab related packages is, that versions in Go dependencies are mostly git commits, and a file like this https://github.com/gogits/gogs/blob/master/.gopmfile defines the dependencies, but i don#t know how often this ocurs
<lfam>From what I've seen, those files are different from project to project. Some projects don't even have them.
<lfam>They also made a serious error only keeping 7 characters of the Git commits.