# Build dependencies: note that bash, bzip2, getconf, grep, tar, and xz are already in /bin and /usr/bin
# 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
# 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
# If the Python version doesn't default to 2, it might be necessary to include Python 2 as a component and then prepend it to the PATH or some similar trick.
../coreutils/buildout.cfg
../coreutils/buildout.cfg
../curl/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
../python3/buildout.cfg
# Runtime dependencies:
# Runtime dependencies:
# TODO: add fonts here once the build works
# TODO: add fonts here once the build works
../fonts/buildout.cfg
../fonts/buildout.cfg
...
@@ -81,7 +80,7 @@ make-binary =
...
@@ -81,7 +80,7 @@ make-binary =
environment =
environment =
# 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
# 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.
# TODO: make sure it's appropriate for SlapOS components to depend on things in /bin, /usr/bin, etc.