| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Generate the environment just once during the build process, and
additionally dump it in shell format to a file.
Load this file when executing nochroot scripts. Such scripts now have
access to config settings, etc.
The default interpreter was changed from sh to bash because shlib uses
bashisms.
|
|
|
|
|
| |
Promote the shared directory to a core directory and create it early,
meaning that it can be used from all stages, including prepare.
|
|
|
|
|
|
|
|
| |
Along the way, add basic support for handling boolean
values in python and shell scripts in modules.
[dsd: trivial tweaks: renamed to --cache-only, use variable presence in
environment for boolean testing, add documentation]
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of listing all the modules in [global].modules,
load all modules specified in the .ini file using [module] notation.
This makes the config file format more friendly to making a build
from various config files specified together, and avoids the annoying
cases when you add a new [configuration section] but forget to add
the module to the module list (not realising your mistake until after
the build has completed).
|
|
|
|
|
|
|
| |
Allow multiple config files to be specified on the command line.
They will be parsed in the order specified.
This replaces the additional-defaults functionality provided before.
|
|
|
|
|
| |
We can now produce post-release releases containing small fixes to
the build system, criteria documented in README.devel.
|
|
|
|
|
|
| |
Emacs swap files, orig/rej files were being processed.
Based on work by Martin Langhoff.
|
|
|
|
|
| |
Running osbuilder under sudo sometimes means a overly-sanitized path,
which can break scripts.
|
| |
|
|
|
|
|
| |
As suggested by Martin Langhoff, we should be using SafeConfigParser
which is more predictable than the now-discouraged ConfigParser.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Path references in the config file can now refer to %(oob_config_dir)s
which resolves to the directory where the config file resides.
Additionally, scripts will find $oob_config_dir defined in the environment.
For example this will find a custom script in the same dir as the config
file:
[custom_scripts]
custom_script_1=%(oob_config_dir)s/myscript.sh
In a custom script, this will apply a patch in the same directory as the
config file:
patch $INSTALL_DIR/etc/foo < $oob_config_dir/foo.patch
[dsd: minor tweak, add documentation]
|
| |
|
|
|
|
| |
This version was used to build OLPC OS 10.1.2 for XO-1 and XO-1.5
|
|
|
|
| |
This version was used to build OLPC OS 10.1.1 for XO-1.5
|
|
|
|
|
| |
This means that the additional defaults file can be used to add modules
to the list, without having to copy the whole list.
|
|
|
|
|
| |
This should allow Chris to specify OLPC-specific configuration
(official=1, signing config) in a less annoying manner.
|
| |
|
| |
|
| |
|
| |
|
|
Basic functionality is working, needs more testing and a comparison
to the OLPC OS 10.1.0 release.
|