bash

Overview

bash is the GNU Bourne Again SHell: a command-line shell and command language interpreter. In a Linux distribution, it usually serves as the interactive shell for users and as the execution environment for many shell scripts and package maintenance tasks. The package exists because many system and build scripts expect a Bash-compatible shell to be available. (gnu.org)

Purpose and typical use cases

Typical use cases for this package include:

• interactive command-line work for administrators and desktop users;
• shell scripting for developers and CI/CD maintainers;
• automation in packaging, build, and deployment workflows;
• running scripts that rely on Bash syntax or Bash-specific features.

Bash is also commonly used as /bin/sh-compatible tooling on systems where scripts are written for a Bourne-style shell, but exact compatibility requirements should be verified by maintainers for each consumer package. (gnu.org)

Upstream project

The upstream project is GNU Bash from the GNU Project. Upstream documentation describes Bash as the shell and command language interpreter for the GNU operating system, with reference manuals and installation documentation published by GNU. (gnu.org)

Upstream reference documentation:

• GNU Bash project page
• GNU Bash manual

Dist-git repository contents

This dist-git repository is organized as follows:

• SPECS/ — RPM spec files and distribution packaging metadata.
• SOURCES/ — source manifests and related metadata used to describe the packaged inputs.
• METADATA/ — repository metadata maintained by the dist-git workflow.
• SBOM/ — software bill of materials data, when present for the package workflow.

Large upstream source archives are intentionally not stored in this Git repository. Instead, the repository keeps source integrity metadata in SOURCES/ manifests so maintainers can verify which upstream inputs belong to the package without checking in the full archive payload. (gnu.org)

Source storage and integrity policy

For this package, NiceOS keeps the upstream payload outside Git and tracks source integrity through the manifests under SOURCES/. This keeps the repository small and reviewable while still recording the expected source inputs.

Before accepting an update, maintainers should verify that:

• the manifest entries still match the intended upstream source set;
• no extra files were introduced or dropped unexpectedly;
• the packaging metadata still refers to the correct upstream project and licensing terms;
• any distro-specific patches are still appropriate for the updated upstream code.

If the package uses generated metadata, maintainers should confirm whether it needs regeneration as part of the update process. If that is unclear, NiceOS maintainers should verify it before relying on the result.

NiceOS maintenance notes

Before updating bash, check the following:

• whether the upstream release changes shell behavior that could affect login shells, non-interactive scripts, or build systems;
• whether any distro patches need rebasing, dropping, or reordering;
• whether configuration files, compatibility wrappers, or script integration points need review;
• whether local packaging rules still match upstream build and installation behavior;
• whether the SBOM metadata, if maintained for this package, needs refresh.

Main risks to consider:

• breaking changes in shell parsing or builtins may affect scripts outside this package;
• subtle compatibility regressions can appear in automation long after the package is built;
• changes in default behavior can affect interactive users and system tooling differently.

If any of these points are uncertain, NiceOS maintainers should verify them before landing the update.

Build and verification checklist

For RPM maintenance work, a practical checklist is:

• inspect the spec file diff for packaging-only changes and unintended behavior changes;
• confirm the upstream source set matches the manifests in SOURCES/;
• rebuild the SRPM and binary RPMs in the target build environment;
• run the package test or smoke-test steps used by NiceOS for shell packages;
• verify that installed files, scriptlets, and ownership paths are still correct;
• check that distro patches still apply cleanly and do not carry stale assumptions;
• validate that the shell starts, runs basic builtins, and can execute representative non-interactive scripts;
• review the generated SBOM or metadata files if the package workflow updates them;
• compare the resulting package contents against previous builds for unexpected file additions or removals.

References

• GNU Bash project page
• GNU Bash manual
• GNU Bash reference manual

Russian documentation

See README_RU.md for the Russian version of this document.

Dist-git repository notes

• Package repository: rpms/bash
• NiceOS branch: niceos-5.2
• This README is intentionally stable and does not include EVR, source archive checksums or lock hashes.