One of the more serious bugs is when you use a pseudo-argument instead of a real triple. So this commit fixes that by checking against an array, and now the build process can default to native triple. Though the script is starting to get bloated. Meh, I dont care. Signed-off-by: Leah Nielson <firstname.lastname@example.org>
|6 days ago|
|OLD||2 weeks ago|
|.gitignore||1 week ago|
|LICENSE||2 weeks ago|
|README.md||2 weeks ago|
|TECH.md||6 days ago|
|template.py||2 weeks ago|
|ziglang.py||6 days ago|
A set of scripts to easily package tons of free software projects.
Note: A rewrite is ongoing and the old scripts have been placed in the OLD/ folder
List of packaged software
I want to write scripts to automatically package software that is not in Debian. The idea being that I could someday launch a debian repository of well-curated packages for users, the packages will be built on and tested on Bookworm (testing) but they should work on Stable and Unstable.
List of software I have successfully packaged: None!
List of software I am currently trying to package:
A build script should be a Python file ideally to maximize code readability and the possibility of adding improvements.
Writing Pythonic code is not required, any code that works and is somewhat easy-to-maintain is ideal.
You could also just add scripts in other languages such as Bash or Nim, just make sure to setup the CI engine to properly execute those. (Ideally a whole new pipeline)
One could even write a packaging script in Woodpecker's format, tho I don't want to be the one to do that.
Ideally, each script should have a header containing essential info about the build dependencies, so they can be easily changed.
Check template.py for a basic header