nitrux/tools

Tools for building our stuff.

Tooling for Nitrux

Tools for building our stuff.

aw          # Run AppImages inside Docker containers.
copier      # Copy binaries and their dependencies to a directory.
execs       # Print the external commands called by the given shell scripts.
mkiso       # Generate bootable ISO images (supports both BIOS and UEFI).
pull        # Download a Docker image as a directory.
runch       # Run commands in a preconfigured chroot.
synth       # Generate ISO images from a configuration file.

The -h will will give you full information about any of these programs.

Issues

If you find problems with the contents of this repository, please create an issue.

©2019 Nitrux Latinoamericana S.C.

tools's Issues

Let mkiso generate the .INFO file used by znx.

It would be very convenient if mkiso handled the .INFO file that znx uses for doing updates.

Given the appropriate data, mkiso should generate the .INFO.

UPDATE_URL="http://the.server/image.iso"
HASH_URL="http://the.server/image.md5sum"
VERSION="this_cool_nitrux_release"

mkiso \
    -v NITRUX \
    -g grub.cfg \
    -u $UPDATE_URL \
    -s $HASH_URL \
    -V $VERSION \
    $ISO_DIR \
    $OUTPUT

Replace chroot with proot on runch.

proot is a much more powerful tool for running processes in an isolated environment. It implements chroot, mount --bind, and binfmt_misc.

• It automatically handles the LFHS mount points.
• It can execute binaries of foreign architectures (e.g. ARMv7 => x86_64).
• It can bind-mount files or directories.

configs folder is not deleted when building ISO

The configs folder is not deleted and is present on the packaged ISO.

Use bcf on synth.

Instead of parsing by hand (which is less than ideal), we should use bcf.

Automatic package manager discovery [synth].

It's very easy to perform automatic discovery of the package manager in the base system. Doing it will alleviate the user from explicitly specifying it.

Change -V flag in mkiso as it may be confused with -v

mkiso in its development branch, has two flags -V and -v which utilize the same letter.

tools/mkiso

Line 15 in 664fe63

echo "Usage: mkiso [-h] [-V label] [-g grub-configuration] [-t path-to-grub-theme] [-u UPDATE_URL] [-s HASH_URL] [-v RELEASE_VERSION] <directory> <output>"

I suggest using -l or -L for label instead to avoid confusion.

Provide packages.

For consistency on all the repositories that use these tools, we should be providing actual packages.

Add a testing set.

The correctness of these scripts should be proven before they get into production environments.

Add BIOS support to mkiso.

mkiso isn't able to create images that are able to boot in BIOS mode, just UEFI.

mkiso should be able to, optionally, add BIOS support to the generated ISO images.

Bash as shell?

All tools use a POSIX compliant shell (/bin/sh) as the command interpreter. The POSIX standard lacks a very useful bash feature: set -o pipefail. That makes a pipe fail if any of its commands fail. OTOH, the POSIX standard states that the pipe's exit code shall be that of the rightmost command. This seems inconsistent if any of the other commands [in the pipeline] fail.