3 ms·
> You can sign built artifacts with cosign without actions or podman[-desktop]/docker. That's all out of scope for, and unrelated to, this build port. > It's
by sgbeal 2y ago
> You can sign built artifacts with cosign without actions or podman[-desktop]/docker.
That's all out of scope for, and unrelated to, this build port.
> It's probably possible to trigger gh actions or gl pipelines builds (container, command) with git repo mirroring.
We maintain our own SCM, which keeps us far removed from the github ways of doing things. None of the SQLite project members actively use github beyond posting the read-only project mirror and occasionally cloning other projects and/or participating in tickets, and that's unlikely to change in any foreseeable future.
> emscripten-forge/recipes/recipes_emscripten/SQLite/build.sh:
Thank you - bookmarked for later perusal and testing.
- westurner 2y agoSame. Thanks What about extensions; does the new build port affect extensions? /? hnlog sqlite (190+ mentions) From https://news.ycombinator.com/item?id=40837610#40842365 https://news.ycombinator.com/item?id=40837610#40842365 : - > There are many extensions of SQLite; rqlite (Raft in Go,), cr-sqlite (CRDT in C), postlite (Postgres wire protocol for SQLite), electricsql (Postgres), sqledge (Postgres), and also WASM: sqlite-wasm, sqlite-wasm-http, dqlite (Raft in Rust), awesome-sqlite
- sgbeal 2y ago> What about extensions; does the new bill port affect extensions? It won't, in any way, affect how third parties use the conventional project headers and amalgamated sources. It only has the potential to affect folks who use the "./configure && make" build process, as differences between the Autotools and Autosetup make it impossible to retain 100% semantic compatibility with the build processes (for reasons described one link removed from the forum post this HN post links to).
- deleted 2y ago[deleted]