split stage0/1 packages into sub-packages

this allows to cross-compile a stage1 without development tools (which might
be interesting to create a rootfs for a single-purpose embedded applicance)
and on the other hand a cross-compiled stage1 with the full set of development
tools (some of which were previously typically built during stage0), by building
the metapackage base-dev together with stage1.

README.md

@@ -173,7 +173,8 @@ it.
 Unlike native compilation, you don't have to build any stages, you can
 immediately start compiling the packages you're interested in. If you intend
 to use the resulting rootfs to boot into, you should however start with building
-`stage1`.
+`stage1`, and if you want to use the resulting rootfs as a full sabotage
+installation with development tools, also the package `base-dev`.
 
 Note that you need to build the `make` and `binutils` packages additional to
 `stage1` if you intend to use the resulting rootfs with full compiler toolchain.

pkg/base-dev

@@ -0,0 +1,7 @@
+[deps]
+jobflow
+sabotage-core
+kernel-headers
+patch
+binutils
+make

pkg/base-sys

@@ -0,0 +1,4 @@
+[deps]
+busybox
+services
+

pkg/stage0

@@ -1,13 +1,8 @@
 [deps.stage0]
-jobflow
-sabotage-core
+base-sys
 services
 stage0-gcc
 stage0-musl
-kernel-headers
-busybox
-patch
-binutils
-make
+base-dev
 
 

pkg/stage1

@@ -1,9 +1,7 @@
 [deps]
-jobflow
-sabotage-core
+base-sys
 kbd
 9base
-busybox
 e2fsprogs
 gcc6
 gmp
@@ -13,10 +11,12 @@ musl
 man
 zlib
 binutils
-patch
 join
 libressl
 ca-certificates
 
+[deps.host]
+base-dev
+
 [build]
 rm -rf "$butch_root_dir""$butch_staging_dir"/stage1