34 |
35 | 
36 |
37 |
59 |
60 | ---
61 |
62 |
36 |
37 | 38 | zeus 39 |
40 | 41 | 42 | **[Wiki][wiki]** 43 | **[Install][installing]** 44 | **[Usage][usage]** 45 | **[FAQ][faq]** 46 | **[Releases][releases]** 47 | **[Issues][issues]** 48 | **[CI][ci]** 49 | 50 | --- 51 | 52 | [![release-badge]][releases] 53 | [![issues-badge]][issues] 54 | [![build-badge]][build] 55 | [![license-badge]][license] 56 | [![help-badge]][help] 57 | 58 |63 | 64 | **Zeus**. A simple AUR helper which utilizes containers allowing developers and users alike to benefit from it's reproducible, clean and flexible builds. To get started with `zeus` follow the [install instructions][installing] or [build it yourself][building]. Be sure to check out the [wiki][wiki] for anything else. 65 | 66 | 67 |
68 | 69 | ## Installing 70 | 71 | Currently there are 2 packages in the AUR. 72 | 73 | - `zeus` - Which builds from the [latest release][latest-release] 74 | - `zeus-bin` - Which unpacks prebuilt binaries from the [latest release][latest-release]. 75 | 76 | | Package | Version | 77 | | :--------: | :---------------------------------: | 78 | | `zeus` | [![pkg-aur-badge]][pkg-aur] | 79 | | `zeus-bin` | [![pkg-bin-aur-badge]][pkg-bin-aur] | 80 | 81 | > **NOTE:** The binaries for `zeus-bin` are built in [Github Actions][build] 82 | 83 | After installing one of the 2 packages, there is one final step towards getting up and running. 84 | 85 | Building the actual builder container. 86 | 87 | ```shell 88 | $ zeus -B 89 | ``` 90 | 91 | > If your user does _**not**_ have access to the docker socket, you will have to run the previous command as root and subsequently every time you want to use the program. 92 | 93 |
94 | 95 | ## Building 96 | 97 | After cloning the repository, use the `build` target in the `Makefile` to build everything. 98 | 99 | ```shell 100 | $ make build 101 | ``` 102 | 103 | > By default the `build` target builds the debug version, if you wish to build the release version set `BUILD_TYPE=release`. 104 | 105 | ```shell 106 | $ export BUILD_TYPE=release 107 | $ make build 108 | ``` 109 | 110 | Testing local changes can be done in 2 ways. 111 | 112 |
113 | 114 | ### Not installing locally 115 | 116 | This method involves no extra steps. 117 | 118 | Running the built binary is as simple as: 119 | 120 | ```shell 121 | $ ./target/$BUILD_TYPE/zeus 122 | ``` 123 | 124 |
125 | 126 | ### Installing locally 127 | 128 | Installing locally for easier testing is possible with the `install` target. 129 | 130 | ```shell 131 | # make install 132 | ``` 133 | 134 | > `DESTDIR` and `PREFIX` can be used to alter the installation. 135 | 136 | After all this you should be able to just run `zeus` directly in the terminal. 137 | 138 | ```shell 139 | $ zeus 140 | ``` 141 | -------------------------------------------------------------------------------- /Vagrantfile: -------------------------------------------------------------------------------- 1 | # -*- mode: ruby -*- 2 | # vi: set ft=ruby : 3 | 4 | Vagrant.configure("2") do |config| 5 | config.vm.box = "archlinux/archlinux" 6 | config.vm.box_check_update = true 7 | 8 | config.vm.synced_folder ".", "/zeus", 9 | sshfs_opts_append: "-o ro -o idmap=user", 10 | type: "sshfs" 11 | 12 | config.vm.provision "shell", inline: <<-SHELL 13 | pacman --needed --noconfirm -Syu base-devel docker 14 | gpasswd -a vagrant docker 15 | sudo systemctl enable docker.service 16 | SHELL 17 | end 18 | -------------------------------------------------------------------------------- /apparmor/zeus: -------------------------------------------------------------------------------- 1 | # vim:syntax=apparmor 2 | # AppArmor policy for zeus 3 | # Auther: threadexio 4 | # Copyright lololol (C) 1337 threadexio 5 | 6 | abi