Archlinux repository server & package build system, written in V.
 
 
 
 
 
 
Go to file
Jef Roosens f736899362
ci/woodpecker/push/build unknown status Details
ci/woodpecker/push/lint unknown status Details
ci/woodpecker/push/builder Pipeline was successful Details
ci/woodpecker/push/publish Pipeline failed Details
Merge pull request 'builder-dockerfile' (#23) from builder-dockerfile into dev
Reviewed-on: Chewing_Bever/vieter#23
2022-01-14 11:32:24 +01:00
.woodpecker Set plugin to correct Dockerfile 2022-01-14 11:31:13 +01:00
src Added development & release image publishing 2022-01-13 13:51:02 +01:00
.dockerignore Added development & release image publishing 2022-01-13 13:51:02 +01:00
.gitignore Working .PKGINFO read function! 2022-01-13 12:35:05 +01:00
Dockerfile Added development & release image publishing 2022-01-13 13:51:02 +01:00
Dockerfile.builder Added builder Dockerfile 2022-01-14 11:20:24 +01:00
Makefile Fixed lint command 2022-01-13 14:33:06 +01:00
README.md Added Dockerfile & custom compiler notice 2022-01-10 08:33:21 +01:00

README.md

Vieter

Vieter is a re-implementation of the Pieter project. The goal is to create a simple PKGBUILD-based build system, combined with a self-hosted Arch repository. This would allow me to periodically re-build AUR packages (or PKGBUILDs I created myself), & make sure I never have to compile anything on my own systems, making my updates a lot quicker.

Why V?

I chose V as I've been very intrigued by this language for a while now. I wanted a fast language that I could code while relaxing, without having to exert too much mental effort & V seemed like the right choice for that.

Custom Compiler

Currently, this program only works with a very slightly modified version of the V standard library, and therefore the compiler. The code for this can be found here. For CI purposes & ease of use, you can also clone & build that repo locally by running make customv.

Features

The project will consist of a server-agent model, where one or more builder nodes can register with the server. These agents communicate with the Docker daemon to start builds, which are then uploaded to the server's repository. The server also allows for non-agents to upload packages, as long as they have the required secrets. This allows me to also develop non-git packages, such as my terminal, & upload them to the servers using CI.