Phil <p...@beadling.co.uk> skribis: > At the risk of cross-posting from skribilo list, whilst our internal > documentation has to remain private, we also have a public fork of guix > which would benefit from some documentation explaining the changes we've made > to guix core code that we hope one day to push upstream - so I've taken > the same technique and applied it here - so people can see a working example: > > This generates the docs with guix imports - see compile-command in the header: > https://github.com/quantiletechnologies/qt-guix/blob/feature/EA-133/compile-docs.scm > > This is the document - it's less ambitious than my internal version in > terms of generating content from guix - but has a few examples of > generating content from channels: > https://github.com/quantiletechnologies/qt-guix/blob/feature/EA-133/qtdocs/qt-guix.skb
Nice! Including channel info in the document like you do here is probably a major use case; it also makes a lot of sense in the context of reproducible research workflows. Looking forward to discussing the ‘qt-guix’ improvements too. :-) Ludo’.
