diff options
| author | Rob Austein <sra@hactrn.net> | 2017-05-15 14:20:10 -0400 |
|---|---|---|
| committer | Rob Austein <sra@hactrn.net> | 2017-05-15 14:20:10 -0400 |
| commit | 8cef9151f6fd927aa31cb07215c87264f29441b8 (patch) | |
| tree | 28906c1eb59dd87ffcfda6afdcc1b31f29a5e4f7 | |
| parent | 8a2ac8efbd0a7de25731036bb0b6b35eae825f51 (diff) | |
README.md explained package build steps in the wrong order.
| -rw-r--r-- | README.md | 10 |
1 files changed, 5 insertions, 5 deletions
@@ -111,11 +111,8 @@ current build process: 3. Loading all of the Debian and Ubuntu packages produced above into the staging instances of a set of APT repositories. -4. Uploading changes from the staging repositories to our public APT - repositories. - -5. Generation of a [Homebrew][] formula and committing that formula to - the staging instance of a Homebrew "tap" (git repository), using a +4. Generation of a [Homebrew][] formula and committing that formula to + the staging instance of a Homebrew "tap" (git repository), using the tarball created during the Debian source package stage as the source package. The Homebrew formula is source-only (no "bottled" binary packages): creating binary packages would not be @@ -124,6 +121,9 @@ current build process: doesn't permit this unless we run our build farm on Apple hardware. +5. Uploading changes from the staging repositories to our public + repositories. + In theory, it would also be possible to produce Windows binaries using the [MinGW][] cross-compilation environment, but Windows is sufficiently different from all other platforms that even minimal Windows support |