From 14f12cc0364fd6f470f7c095494a78845b1fe85b Mon Sep 17 00:00:00 2001 From: aethrvmn Date: Sun, 16 Nov 2025 22:36:58 +0100 Subject: update README --- README | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) (limited to 'README') diff --git a/README b/README index 849b92b..ac8b95d 100644 --- a/README +++ b/README @@ -5,3 +5,21 @@ It is a work in progress. Currently, mostly git and it's dependencies are packag The other targets are the packages defined in the LFS book, and programming languages like nim and rust. The scope of tesserae does not include an installer for mosaic, nor for the cross-compilation steps of LFS. These might be in a different project (?) + +As of now a tessera requires the following: + +source: string # the source url (in the future also can be a local path) +patches: seq[string] # the source urls for the patches (also local in the future probably) +dependencies: seq[string] # list of dependencies to be built before the package +build: seq[string] # the list of commands in the order they are meant to be run +result: string # an identifier output bin or lib to verify installation + +The above "works" for a traditional distro setup, but not for a declerative distro, since the aim is to build a bin and its deps in a single sha256-pkgName folder structure, like Guix/Nix + +The final shape is probably going to be more like: + +source: string +patches: seq[string] +dependencies: seq[string] +dependants: seq[string] # mostly for the core/ tessera and updates cascading. tbh this may or may not make it because you can just walk the graph backwards. +build: seq[string] -- cgit v1.2.3