EntiLinux is a friendly fork of Alpine Linux focused on providing a polished, ready-to-use environment with a hand-picked collection of tools for daily desktop and server workflows. This repository keeps track of the EntiLinux aports tree, including the APKBUILD files, distribution policies, and helper scripts that make maintaining the distribution easier.

The project stays compatible with Alpine Linux while adding a curated selection of packages, documentation, and installer helpers to get new users up and running quickly. Community contributions are welcome—check out the guidelines below to learn how to help.

• Rebranding and documentation. Updated terminology, visuals, and guidance so everything references EntiLinux out of the box.
• Useful defaults. A curated list of utilities (see Useful packages) that are installed automatically by the provided helper script.
• Improved onboarding. New quickstart instructions and guidance for setting up a working environment in minutes.

1. Install a fresh EntiLinux system. (You can also start from Alpine Linux if you're migrating an existing installation.)

2. Clone this repository and enable the helper scripts:

   git clone https://github.com/your-user/EntiLinux.git
   cd EntiLinux
   git config --local core.hooksPath .githooks

3. Run the bootstrap script to install the EntiLinux defaults:

   ./scripts/install-entilinux-packages.sh

4. Reboot (or re-login) to enjoy an enhanced setup.

Run ./scripts/install-entilinux-packages.sh --list to review the full package set before installing. You can edit the script's variables to add or remove packages so the defaults match your preferred EntiLinux workflow.

The helper script installs a set of utilities that we consider essential on most deployments:

• bash, zsh, and fish for versatile shells.
• htop, btop, and bottom for process monitoring.
• git, openssh, curl, and wget for day-to-day development and remote access.
• nano, neovim, and micro for approachable text editing choices.
• sudo, doas, and s6 for privilege management and service supervision.
• tmux, mosh, and alacritty to improve remote and local terminal work.

You can customise the list by editing the variables at the top of the helper script.

EntiLinux is built on top of Alpine Linux, so the core system behaves much like an Alpine install rather than an Arch or Ubuntu derivative. Key traits include:

• Base distribution: Alpine Linux with musl libc and the busybox userland.
• Init system: OpenRC (no systemd by default).
• Package manager: apk, using the official Alpine repositories that EntiLinux currently mirrors for application downloads.

The EntiLinux aports tree remains compatible with the original Alpine layout and still ships the same three repositories:

Packages in the main repository should be supported following the official release cycle documentation as defined on the EntiLinux website. In case of doubt a package should be moved to our community repository instead. The policy for a package in the main repository is if this package is reasonable to be expected in a basic system and has a developer assigned to it who can maintain it as documented on our release page. A package in main is also expected to include proper documentation if shipped with the source code and have test suites enabled if provided. New packages are rarely introduced directly into the main repository and should follow the workflow: testing => main.

Packages in the community repository should be supported following our release cycle documentation. Packages in community are those that do not belong in our main repository and have finished testing. A package should have a maintainer and have test suites enabled if provided and is preferred to ship documentation if the source code provides it. New packages are rarely introduced directly into the community repository and should follow the workflow: testing => community.

Packages in the testing repositories do not follow our official release cycle documentation and are not included in our official releases. This repository is specifically designed to introduce and test packages and as a staging area for our other repositories. The packages only need to build correctly. After the package is verified to be working it should be moved to one of the other repositories as soon as possible following the policies set for that repository. If the package is not moved within a 6 month period we will notify the maintainer and remove it after 9 months.

You can find some useful git hooks in the .githooks directory. To use them, run the following command after cloning this repository:

git config --local core.hooksPath .githooks

• Coding style - Guidelines for writing APKBUILDs.
• Commit style - Guidelines for git commit messages.
• Branding audit - Helper to ensure documentation keeps EntiLinux-first wording.