# Build dependencies: note that bash, bzip2, getconf, grep, tar, and xz are already in /bin and /usr/bin
# TODO: I think findutils is only here to expose xargs, which is already in /usr/bin, so see if we can get away with not requiring it
../coreutils/buildout.cfg
../coreutils/buildout.cfg
../curl/buildout.cfg
../depot_tools/buildout.cfg
../depot_tools/buildout.cfg
../git/buildout.cfg
../git/buildout.cfg
../gperf/buildout.cfg
../gperf/buildout.cfg
../pkgconfig/buildout.cfg
../pkgconfig/buildout.cfg
../python-2.7/buildout.cfg
../python-2.7/buildout.cfg
../python3/buildout.cfg
../python3/buildout.cfg
# Runtime dependencies:
# TODO: add fonts here once the build works
../fonts/buildout.cfg
../fontconfig/buildout.cfg
../nspr/buildout.cfg
../nspr/buildout.cfg
../nss/buildout.cfg
../nss/buildout.cfg
parts =
parts =
chromium
chromium-wrapper
# TODO: it may be more appropriate to manage our own copy of depot_tools, because I think some of the "gclient sync" commands may modify depot_tools, which could be problematic if other components or software releases depend on a shared copy, and at any rate it causes some build errors: when updating depot_tools, git complains because HEAD has been moved. Is there a way to guarantee a private copy? (This may be a moot point, since I don't think it's used by anything else, anyway, and trying again fixes the git issue.)
# There's nothing special about version 91.0.4472.132. It just happened to be
# There's nothing special about version 91.0.4472.132. It just happened to be
# the current Chromium stable version at the time of writing.
# the current Chromium stable version at the time of writing.
# Possible foot-gun: if you specify PATH=...:$PATH, it will literally insert the string '$PATH' on your PATH; buildout won't do the expansion unless you use %(PATH)s
# TODO: make sure it's appropriate for SlapOS components to depend on things in /bin, /usr/bin, etc.