On 2016-11-15 04:57, l...@gnu.org wrote:
Hello!
Luis Felipe López Acevedo <felipe.lo...@openmailbox.org> skribis:
I cloned the website to try a fix for bug #22115, and wanted to ask
first what process do you follow to try out the whole website locally?
When I build and serve the website with Haunt, I face the following
problems:
1. Pages don't load static files because they are looking for the
"static" directory in "/software/guix/static". Do I need to set some
variable first?
To test locally, you need to do:
$ GUIX_WEB_SITE_LOCAL=yes haunt build
$ haunt serve
There should be no broken links, except for links to the manual or
other
parts of gnu.org.
I suppose this should go to README…
2. The Packages and Packages Issues pages, which are defined in (www
packages) are commented out. How do you deal with those in
development?
That’s on purpose, so that people don’t need to have Guix installed to
hack on the web site.
We build these pages separately using the ‘export-web-page’ procedure.
Ludo, I'm not sure how to do this part. Do I just import (www) and (www
packages) in a REPL, and call `export-web-page` for each page (packages
index and issues)? You don't have to modify `www.scm` at all (uncomment
elements in the %web-pages list, for example)?
Also, trying just that, when I try importing (www packages), (guix ui)
is not found in my system:
scheme@(guile-user)> (use-modules (www packages))
;;; compiling
/home/anonimo/Documentos/guix-artwork/website/www/packages.scm
;;; WARNING: compilation of
/home/anonimo/Documentos/guix-artwork/website/www/packages.scm failed:
;;; ERROR: no code for module (guix ui)
While compiling expression:
ERROR: no code for module (guix ui)
I'm using Guile 2.0.13 installed from Guix binary on Debian 8, and guix
is version 20161113.19. Where are Guix modules?
Thanks,
--
Luis Felipe López Acevedo
http://sirgazil.bitbucket.org/
