Build and packaging library
- Python 55.2%
- Makefile 32.4%
- Shell 12.4%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
Jan Lindemann
9961d4b5f4
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 5m31s
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 4m42s
CI / Packaging test (pull_request) Successful in 0s
CI / Packaging - Kali Linux (push) Successful in 5m7s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 4m25s
CI / Packaging test (push) Successful in 0s
A workspace project directory that has a Makefile but no package proofs - no project.conf, no VERSION - is buildable with a plain make, yet the build fails on it: calculate_order() walks the requested modules, and the walk in App.__get_project_refs() raises an unmet dependency, because the installation state of such a project is unprovable. The walk has to stay strict: its proofs are package proofs, and loosening App.is_installed() would weaken the unmet dependency detection for every get_project_refs() caller. This commit therefore keeps the tolerance in the build: before calculating the order, run() partitions the requested modules. A module that is not installed in any flavour but resolves to a workspace directory with a Makefile is appended to the build order as a dependency-less leaf and built with a plain make; modules without any directory at all still raise the unmet dependency error. A jw dependency declared in a project.conf on such a project still raises, which is correct: it is a declared dependency on a package that does not exist. Assisted-by: unsloth/Qwen3.8-27B-GGUF:Q4_K_M with pi.dev v0.85.1 Signed-off-by: Jan Lindemann <jan@janware.com> |
||
| .github/workflows | ||
| bin | ||
| conf | ||
| doc | ||
| make | ||
| scripts | ||
| src | ||
| test | ||
| .gitignore | ||
| HASH | ||
| Makefile | ||
| RELEASES | ||
| VERSION | ||