]> git.sev.monster Git - abchr.git/blame - README.MD
update readme
[abchr.git] / README.MD
CommitLineData
fb547c12 1# abchr
2
3There are various build chains surrounding Alpine. Most solutions use
4containerization, QEMU, and other technologies; meanwhile I just wanted a
5simple way to build packages and install development utilities without shitting
6up my production system. `abchr` is an attempt to create a simple solution to
7my simple problem. It isn't very flexible, requires root access for chroot, and
8won't allow you to (easily) build for multiarch, but it works.
9
10## Installation
11
121. Create a directory and 3 subdirectories named `bin`, `alpine`, and `aports`.
13 Your tree should look like this:
14 ```
15 + abchr
16 + bin
17 + alpine
18 + aports
19 ```
202. Clone the repo to the `bin` directory.
fd849742 213. Run `abchr-newchroot $(id -u)` to populate the `alpine` directory with a new
fb547c12 22 installation of Alpine Linux. This processes downloads the latest
23 `apk-tools-static` into the chroot and installs the basic packages necessary
fd849742 24 for a build environment. It also creates a user in the chroot with its UID
25 set to the first argument of the script. Having this be your own UID is
26 optimal as it lets you manupulate the chroot files easily.
fb547c12 274. To ensure everything worked, run `abchr abuild -h`. You should see the help
28 text for `abuild`, which should be installed in the chroot.
fd849742 29
30## Usage
31
32The `abchr` command simply sets up the chroot and starts whatever program is
33specified in the arguments as-is. There are some exceptions, meant for ease-of-
34use; run `abchr -h` to see what the script is capable of.
This page took 0.047038 seconds and 4 git commands to generate.