pthbs

Packaging Through Hashed Build Scripts
git clone https://ccx.te2000.cz/git/pthbs
Log | Files | Refs | Submodules | README

commit 481e666b5eaa6db28b62cd1d03b9c9fc58e6ae68
parent 415aa73341f79bee0d914fe60cbdcce4412f695d
Author: Jan Pobříslo <ccx@te2000.cz>
Date:   Thu, 15 Jun 2023 01:45:42 +0200

Clarify README

Diffstat:
MREADME | 6+++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README b/README @@ -19,8 +19,8 @@ How this works -------------- Each package definition is actually a shell script that has all the instructions -to build the software in question as well as hash of any sources it needs, -either in form of file sha256sum or of git commit id. +to build the software in question as well as hash of any installed software or +sources it needs, either in form of sha256sum or git commit id. This shell script is then hashed with sha256 and the result is appended to package name to form unique installation directory for that specific @@ -100,5 +100,5 @@ Planned features * build sandbox * fully reproducible builds -* rewrite Python package generator into something easier to bootstrap on +* rewrite Python package generator into something easier to bootstrap with on POSIX-ish system (AWK?)