Hi! I use NixOS and would like to consume .npk releases without bypassing Nix's declarative package management.
As I understand the README, npack install writes package files to the host system, a user-local prefix, or an isolated store. On NixOS, I would instead want Nix to fetch a pinned artifact, verify it, and manage the resulting installation.
Would you consider a way for npack to export the information needed by a Nix derivation or flake? An initial version could expose the publisher key, package name, version, artifact URL, SHA-256 hash, platform, dependencies, and the result of verifying the signed release metadata. Nix could then fetch and unpack the artifact into its own store.
This would keep Nostr and Blossom as the release and discovery layer while leaving installation and rollback to Nix. It might also provide a useful starting point for other immutable or declarative systems.
Is this compatible with your plans for the package format? I would be interested in helping test a NixOS integration.
Hi! I use NixOS and would like to consume
.npkreleases without bypassing Nix's declarative package management.As I understand the README,
npack installwrites package files to the host system, a user-local prefix, or an isolated store. On NixOS, I would instead want Nix to fetch a pinned artifact, verify it, and manage the resulting installation.Would you consider a way for
npackto export the information needed by a Nix derivation or flake? An initial version could expose the publisher key, package name, version, artifact URL, SHA-256 hash, platform, dependencies, and the result of verifying the signed release metadata. Nix could then fetch and unpack the artifact into its own store.This would keep Nostr and Blossom as the release and discovery layer while leaving installation and rollback to Nix. It might also provide a useful starting point for other immutable or declarative systems.
Is this compatible with your plans for the package format? I would be interested in helping test a NixOS integration.