From 7e56cfdba2434e8ada7a0202aefc7ae671b04b2e Mon Sep 17 00:00:00 2001 From: deep-42-thought Date: Tue, 16 May 2017 15:14:16 +0200 Subject: Updated Release engineering (markdown) --- Release-engineering.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Release-engineering.md b/Release-engineering.md index 39a9125..9fd6d44 100644 --- a/Release-engineering.md +++ b/Release-engineering.md @@ -4,6 +4,8 @@ After that, we simply switch to our own i686 repository. The generation of the iso is simple: We forked [archiso32](https://github.com/archlinux32/archiso32) from the official [archiso](https://git.archlinux.org/archiso.git/) tool to produce ISO images. After [this change](https://lists.archlinux.org/pipermail/arch-releng/2017-January/003763.html) was committed, we simply skipped all commits related to the removal of i686 support. -Possibly we may drop support for `x86_64` to get smaller images which fit on a standard cd. -We then run the command with the default configuration, which will produce a working i686 ISO hopefully. -We might use bittorrent for the distribution of the iso, too. \ No newline at end of file + +There are two branches: [master](https://github.com/archlinux32/archiso32/tree/master) (for i686 only) and [dual-boot](https://github.com/archlinux32/archiso32/tree/dual-boot) (for dual bootable images). +Accordingly, there are two packages `archiso32` and `archiso-dual` hosted at [archlinuxewe](https://arch.eckner.net/archlinuxewe/os/x86_64/) for building the isos (as with the original scripts, they're meant to be run under x86_64). + +At some point, we might use bittorrent for the distribution of the iso, too. \ No newline at end of file -- cgit v1.2.3