| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is the same idea as 497a49162f7c8b5c1d7c653087b0ac6c8e5765f9.
Without this patch, the following errors occur when running index.sh:
sed: 1: "news/new-mailing-lists. ...: extra characters at the end of n command
sed: 1: "news/andrew-robbins-new ...: extra characters at the end of n command
sed: 1: "news/formalised-structu ...: extra characters at the end of n command
sed: 1: "news/proposal-rejoin-gn ...: extra characters at the end of n command
sed: 1: "news/unity.bare.html": extra characters at the end of n command
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Before the Makefile, publish.sh was executed on markdown source
files using find(1), which happened like this:
./publish.sh ./index.md
Now that we have a Makefile, this happens instead:
./publish.sh index.md
Note that the file argument "index.md" in the first and second case
both refer to the same file, yet they are different strings. This is
important because publish.sh gives index.md (among other files) special
treatment, and it does this by string comparison.
Unfortunately, only the argument in the first case ("./index.md") will
cause publish.sh to give special treatment, while the argumnent in the
second case ("index.md") will not.
To fix this, make it so that both "./index.md" and "index.md" trigger
publish.sh's special handling. This commit also fixes the same issue
for "docs/fdl-1.3.md" and "conduct.md".
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is done by replacing www/generate.sh with a Makefile. Benefits:
- Makes builds incremental, meaning that only the minimum number of
markdown files will be converted to HTML during a build. The previous
scheme always generated a new HTML file for every markdown file,
which is a big waste of time if only 1 or 2 markdown files have been
changed.
- Allows for much faster builds through concurrent jobs (e.g., via
"make -j4"). On my 4-core machine, my average build time for the
website with generate.sh was just over 26 seconds; with "make -j4",
it was 13 seconds.
- Avoids portability issues with find(1) in generate.sh, which I was
encountering on OpenBSD.
A note on portability: unlike GNU Make, OpenBSD's Make does not have
the "$(shell [commands])" construct, so we don't use that. Instead we
use "!= [commands]", which is supported by both.
|
| | |/
| |
| |
| |
| |
| | |
Instead of always using the same file (temp.md), use a unique temporary
file so that multiple instances of publish.sh do not clobber each
other's work.
|
| |\ \
| |/
|/| |
|
| |/ |
|
| |\ |
|
| |/
|
|
| |
They are generated files, so should probably not be tracked.
|
| |\ |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On OpenBSD, publish.sh errors out at the following call
to sed(1) (from "bash -x publish.sh"):
+ sed temp.md -i -e 's/\.md\(#[a-z\-]*\)*)/.html\1)/g'
sed: 1: "temp.md": undefined label 'emp.md'
It seems that "temp.md" is being parsed by sed as a sed command,
not as a named file. This is likely due to OpenBSD's strict
usage requirements for sed:
usage: sed [-aEnru] [-i[extension]] command [file ...]
sed [-aEnru] [-e command] [-f command_file] [-i[extension]] [file ...]
As shown above, the sed command must always come before any named
files. This commit does that, which fixes publish.sh with OpenBSD's sed.
This is also tested and working with GNU sed v4.2.2
|
| |\ |
|
| |/
|
|
|
|
|
| |
OptiPNG losslessly optimizes .png files; in other words, the images
in question should (and do, by my testing) look the same.
In short, we save some bytes for free.
|
| |\ |
|
| | |
| |
| |
| |
| | |
Be consistent with marking up commands as such, so the documentation
is less surprising.
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| | |
The openbsd1 partition is only present for users with an MBR
installation of OpenBSD, which not everyone has.
|
| | |
| |
| |
| | |
Avoid jargon, add markup where applicable, rewrite for brevity, etc.
|
| | |
| |
| |
| | |
Because why not?
|
| | |
| |
| |
| |
| | |
Other command lines are marked up similarly in openbsd.md, so "dd"
should be as well.
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| | |
The grub.conf mentioned here has the same errors that the OpenBSD
one had.
|
| | |
| |
| |
| |
| | |
There were some weird special characters which messed things up.
Replacing them with spaces fixes the problem.
|
| |/
|
|
|
| |
Previously, Libreboot's GRUB payload would fail to detect the
OpenBSD menuentry. Now it does.
|
| |\ |
|
| |/ |
|
| |\ |
|
| |/ |
|
| |\ |
|
| | | |
|
| |/
|
|
| |
i.e., source tarballs are (partially) supported
|
| |\ |
|
| |/
|
|
|
| |
Will help facilitate sane code when handling: archive formats,
checksum file extensions, signature formats.
|
| |\
| |
| |
| | |
master
|
| |/ |
|
| |\
| |
| |
| | |
master
|
| |/ |
|
| |\ |
|
| |/
|
|
|
| |
This is mainly useful for being able to run these scripts on BSDs.
And for users who use a Bash not installed to /bin.
|
| |\ |
|
| | | |
|
| |\ \ |
|
| |/ /
| |
| |
| |
| | |
This reverts part of pull request #217 which called the 'env'
binary for each printf invocation.
|
| |\ \ |
|
| |/ /
| |
| |
| | |
Continuation of pull request #217 re: printf usage.
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
All printf calls should now be properly formatted; prior, the
format specifier string was erroneously used for both the format
specifiers and the string to be printed. 'env' is now used to
locate the printf binary so as to avoid potentially using a shell
builtin. Lastly, all calls to 'echo' within the new build system
have been replaced with printf for consistency/portability purposes.
|
| |\ \ \ |
|
