Hi,
On Tue, 29 Jan 2019 14:57:17 +0100 lundi wrote:
> A new day, some new questions. First up, Chicken version is 4.13.0.
>
> For my wip egg, I'm trying to auto-generate docs with hahn.
> This works fine as far as running hahn from command line is
> concerned. However, things fail when trying to invoke hahn through
> salmonella via setup-helper.
>
> My .meta contains (depends hahn) and my .setup looks pretty much like
> in the example given on the hahn eggref. Running salmonella generates
> no .wiki file. Checking salmonella.log reveals:
>
>
> Error: (require) cannot load extension: alist-lib
> Call history:
> bin/hahn.scm:3: ##sys#require <--
> Warning: Documentation not generated: shell command failed with
> nonzero exit status 17920:
> hahn -o xmkit.wiki xmkit.scm
> This may be because hahn-utils is not installed.
>
>
> Obviously hahn-utils is installed, otherwise I couldn't run hahn from
> command line. So let's check that alist-lib. chicken-install alist-lib
> gives me:
Note that salmonella uses an isolated local egg repository to test eggs,
so that it can catch dependency problems. I'd guess the hahn-utils
executable you are using is from your CHICKEN installation prefix, not
from the environment that salmonella uses. Is that correct? If so,
that would explain why you can run hahn-utils but salmonella can't.
> The following installed extensions are outdated, because `alist-lib'
> requires later versions:
> hahn (0.5.3 -> 0.9.3)
>
> Do you want to replace the existing extensions? (yes/no/abort) [no]
>
>
> Uh, what? Ok, let's replace hahn. Afterwards I also need to reinstall
> hahn-utils because "updating" hahn appearantly removes it. Now,
> running salmonella again still results in the same error. And
> likewise, another chicken-install alist-lib will still complain about
> hahn being outdated.
> Note that alist-lib is actually installed and usable from csi.
>
> So, any way I can get out of this loop? Am I missing anything?
I don't know how hahn/hahn-utils work, but both seem to be ok according
to you test system [1][2]. It seems that you are using hahn-utils, but
you have hahn in your dependency specification. According to the
dependency graphs, hahn-utils depends on hahn, not the other way around
[3][4]. It's possible that hahn is documented using itself, and that it
would optionally use hahn-utils (that would be a circular dependency),
but I'm not sure about that.
[1]
https://salmonella-linux-x86-64.call-cc.org/chicken-4-debugbuild/gcc/linux/x86-64/2019/01/29/salmonella-report/install/hahn.html
[2]
https://salmonella-linux-x86-64.call-cc.org/chicken-4-debugbuild/gcc/linux/x86-64/2019/01/29/salmonella-report/install/hahn-utils.html
[3]
https://salmonella-linux-x86-64.call-cc.org/chicken-4-debugbuild/gcc/linux/x86-64/2019/01/29/salmonella-report/dep-graphs/hahn-utils.html
[4]
https://salmonella-linux-x86-64.call-cc.org/chicken-4-debugbuild/gcc/linux/x86-64/2019/01/29/salmonella-report/dep-graphs/hahn.html
> I'm not subscribed to hahn, in any case. But I do want to
> auto-generate pretty-looking wiki pages (with rainbow parens, yay!)
> from in-source documentation, if possible.
>
> Also a slightly related question, is it possible to pass the
> salmonella's documentation step when linting locally, or does the
> documentation need to be available in the svn repo?
The documentation must be available in our wiki. The test that checks
for the availability of documentation is basically a HEAD request.
All the best.
Mario
--
http://parenteses.org/mario
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
