GNUBoot/gnuboot
GNUBoot
/
gnuboot
mirror of https://git.savannah.gnu.org/git/gnuboot.git
2
1
Fork 0
Code Issues Releases Activity
gnuboot/website/.gitignore

15 lines
180 B
Plaintext
Raw Normal View History

Import website-build to build the GNU Boot website. Having that code inside the same repository than GNU Boot makes it easier to keep Untitled versions (and possibly additional patches on top) in sync with the documentation/website being worked on. This is relevant as there are plans within GNU Boot to convert the website to Texinfo but that would require to patch untitled (to add support for Texinfo pages in untitled) to do a progressive transition to Texinfo. Using an external repository to temporarily maintain a patched version of Untitled is not optimal as we would end up having to warn users not to use that repository anymore at some point. Bringing in the whole untitled source code and documentation in this GNU Boot repository is also not a good option since we only need minimal patching on top of untitled, so in the long run not doing that would help keep the GNU Boot repository smaller and more simple. In addition we currently do need to wrap the build with a fixed Guix revision as for instance with a more recent Guix revision than the one used by website-built, for instance at the commit ("gnu: nyxt: Update to 3.9.0."), if we run ./build.sh directly without using a fixed Guix revision, the build is broken: Generating 'www/lbwww/site/index.html' Generating 'www/lbwww/site/license.html' YAML parse exception at line 7, column 0, while scanning a simple key: could not find expected ':' Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> Acked-by: Adrien 'neox' Bourmault <neox@gnu.org>
2023-10-12 17:13:11 +02:00
/aclocal.m4
Merge website and website-build. Before being merged with the commit dc6e1f32c151c5245e5936fb4e80a2b5f32984e2 ("Import website-build to build the GNU Boot website."), website-build was a separate git repository. And so, even after the merge, until the commit 20d122e94a39bfc0cbecd1bf8f39bafa7e597c72 ("website-build: use website from local git repository."), it still worked in the same way and still downloaded the website from git. This prevented merging the website and website-build directories together as the GNU Boot repository also needed to be a valid Untitled website repository as well. Now after this commit, the website is built from the same git tree, so we can simply adjust the build scripts to be able to move things around. In addition of making things more clear for contributors, it also simplify the migration to haunt as with haunt we typically have the haunt.cfg (and the autotools build code if needed) code in the top directory and the markdown files in a subdirectory. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> Acked-by: Adrien 'neox' Bourmault <neox@gnu.org>
2024-06-03 21:16:00 +02:00
/autom4te.cache/
Import website-build to build the GNU Boot website. Having that code inside the same repository than GNU Boot makes it easier to keep Untitled versions (and possibly additional patches on top) in sync with the documentation/website being worked on. This is relevant as there are plans within GNU Boot to convert the website to Texinfo but that would require to patch untitled (to add support for Texinfo pages in untitled) to do a progressive transition to Texinfo. Using an external repository to temporarily maintain a patched version of Untitled is not optimal as we would end up having to warn users not to use that repository anymore at some point. Bringing in the whole untitled source code and documentation in this GNU Boot repository is also not a good option since we only need minimal patching on top of untitled, so in the long run not doing that would help keep the GNU Boot repository smaller and more simple. In addition we currently do need to wrap the build with a fixed Guix revision as for instance with a more recent Guix revision than the one used by website-built, for instance at the commit ("gnu: nyxt: Update to 3.9.0."), if we run ./build.sh directly without using a fixed Guix revision, the build is broken: Generating 'www/lbwww/site/index.html' Generating 'www/lbwww/site/license.html' YAML parse exception at line 7, column 0, while scanning a simple key: could not find expected ':' Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> Acked-by: Adrien 'neox' Bourmault <neox@gnu.org>
2023-10-12 17:13:11 +02:00
/config.log
/config.status
/configure
/id_oauth2_bearer
/install-sh
/lighttpd.conf
/Makefile
/Makefile.in
/missing
website-build: serve.sh: remove the need for random temporary directory. Since we are migrating to haunt and that haunt builds the website in site/ we also use that. In addition that also simplifies the lighttpd configuration. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> Acked-by: Adrien 'neox' Bourmault <neox@gnu.org>
2024-05-19 15:11:24 +02:00
/site/**
Merge website and website-build. Before being merged with the commit dc6e1f32c151c5245e5936fb4e80a2b5f32984e2 ("Import website-build to build the GNU Boot website."), website-build was a separate git repository. And so, even after the merge, until the commit 20d122e94a39bfc0cbecd1bf8f39bafa7e597c72 ("website-build: use website from local git repository."), it still worked in the same way and still downloaded the website from git. This prevented merging the website and website-build directories together as the GNU Boot repository also needed to be a valid Untitled website repository as well. Now after this commit, the website is built from the same git tree, so we can simply adjust the build scripts to be able to move things around. In addition of making things more clear for contributors, it also simplify the migration to haunt as with haunt we typically have the haunt.cfg (and the autotools build code if needed) code in the top directory and the markdown files in a subdirectory. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> Acked-by: Adrien 'neox' Bourmault <neox@gnu.org>
2024-06-03 21:16:00 +02:00
/untitled/
/website.tar.gz