A fork of Raspberry Pi OS that runs OctoPrint and a GUI
Find a file
Joseph Carter abc3e45727 build.sh: Support comments in package files (#14)
* build.sh: Support comments in package files

This patch allows the use of hash comments inside patch files.  It's a
little ugly, but it strips comments and collapses all whitespace down to
single space characters between package names.  It handles comments
anywhere in a line, as well.

Was unsure if \ continuation of the long sed line or the inclusion of a
couple of lines of comments explaining what the sed expressions are
doing would be appreciated, so didn't include them in this patch.

* build.sh: whitespace fix

* build.sh: Use sed script for packages files

Broke the sed expressions out of build.sh and put them their own
documented sed script.  This greatly improves readability and avoids
build.sh getting messier.

Broke the substitution command into two separate subs.  The first just
deletes comments, and the second collapses all whitespace into a single
space.  This too is easier to read, and catches a couple of edge cases
that would result it not all whitespace being collapsed.  The result may
still have (one) leading and/or trailing space, which is acceptable.
2016-09-08 06:32:36 +10:00
export-image hardlink documentation 2016-05-19 19:45:54 +01:00
export-noobs export-noobs: ensure STAGE_WORK_DIR exists 2016-05-27 13:22:06 +01:00
scripts build.sh: Support comments in package files (#14) 2016-09-08 06:32:36 +10:00
stage0 Add Raspbian stages 2016-04-11 07:34:01 +01:00
stage1 Rework 2016-05-05 21:21:42 +01:00
stage2 Rework 2016-05-05 21:21:42 +01:00
stage3 Add Raspbian stages 2016-04-11 07:34:01 +01:00
stage4 Add python spidev packages 2016-05-17 15:01:30 +01:00
.gitignore Various fixes 2016-05-04 19:52:13 +01:00
build.sh build.sh: Support comments in package files (#14) 2016-09-08 06:32:36 +10:00
README.md README.md: Working toward basic documentation (#10) 2016-09-05 14:02:39 +10:00

#TODO

  1. Simplify running a single stage
  2. Documentation

#Dependencies

quilt kpartx realpath qemu-user-static debootstrap zerofree pxz

#Config

Upon execution, build.sh will source the file config in the current working directory. This bash shell fragment is intended to set needed environment variables.

The following environment variables are supported:

  • IMG_NAME, the name of the distribution to build (required)
  • APT_PROXY, proxy/cache URL to be included in the build

A simple example for building Raspbian:

IMG_NAME='Raspbian'

#Stage Anatomy

#Raspbian Stage Overview

The build of Raspbian is divided up into several stages for logical clarity and modularity. This causes some initial complexity, but it simplifies maintenance and allows for more easy customization.

  • Stage 0, bootstrap. The primary purpose of this stage is to create a usable filesystem. This is accomplished largely through the use of debootstrap, which creates a minimal filesystem suitable for use as a base.tgz on Debian systems. This stage also configures apt settings and installs raspberrypi-bootloader which is missed by debootstrap. The minimal core is installed but not configured, and the system will not quite boot yet.

  • Stage 1, truly minimal system. This stage makes the system bootable by installing system files like /etc/fstab, configures the bootloader, makes the network operable, and installs packages like raspi-config. At this stage the system should boot to a local console from which you have the means to perform basic tasks needed to configure and install the system. This is as minimal as a system can possibly get, and its arguably not really usable yet in a traditional sense yet. Still, if you want minimal, this is minimal and the rest you could reasonably do yourself as sysadmin.

  • State 2, lite system. This stage produces the Raspbian-Lite image. It installs some optimized memory functions, sets timezone and charmap defaults, installs fake-hwclock and ntp, wifi and bluetooth support, dphys-swapfile, and other basics for managing the hardware. It also creates necessary groups and gives the pi user access to sudo and the standard console hardware permission groups.

    There are a few tools that may not make a whole lot of sense here for development purposes on a minimal system such as basic python and lua packages as well as the build-essential package. They are lumped right in with more essential packages presently, though they need not be with pi-gen. These are understandable for Raspbian's target audience, but if you were looking for something between truly minimal and Raspbian-lite, here's where you start trimming.

  • Stage 3, desktop system. Here's where you get the full desktop system with X11 and LXDE, web browsers, git for development, Raspbian custom UI enhancements, etc. This is a base desktop system, with some development tools installed.

  • Stage 4, complete Raspbian system. More development tools, large packages like LibreOffice, email, sonic-pi, wolfram-engine, etc. All the things.