Struct Store 

pub struct Store { /* private fields */ }

Resolves and (lazily) creates the standard ~/.stryke/... layout.

Implementations

impl Store

pub fn user_default() -> PkgResult<Store>

Construct a Store rooted at ~/.stryke/. Honors the STRYKE_HOME environment variable for tests and CI sandboxes.

pub fn at(root: impl Into<PathBuf>) -> Store

Construct a Store rooted at an explicit path (used by tests).

pub fn root(&self) -> &Path

root — see implementation.

pub fn store_dir(&self) -> PathBuf

store_dir — see implementation.

pub fn cache_dir(&self) -> PathBuf

cache_dir — see implementation.

pub fn git_dir(&self) -> PathBuf

git_dir — see implementation.

pub fn bin_dir(&self) -> PathBuf

bin_dir — see implementation.

pub fn index_dir(&self) -> PathBuf

index_dir — see implementation.

pub fn package_dir(&self, name: &str, version: &str) -> PathBuf

Path where a package extraction lives: ~/.stryke/store/{name}@{version}/.

pub fn ensure_layout(&self) -> PkgResult<()>

Ensure the full directory layout exists. Idempotent. Called eagerly by s install; tests exercise it directly.

pub fn has_package(&self, name: &str, version: &str) -> bool

True if a name@version extraction already exists in the store.

pub fn install_path_dep( &self, name: &str, version: &str, src: &Path, _manifest: &Manifest, ) -> PkgResult<PathBuf>

Copy a path-dep into the store as name@version using the canonical release-tarball layout, so s install -g . produces a byte-for-byte equivalent on-disk shape to s install -g github.com/<owner>/<repo>. Exactly three things land in the store and nothing else (no target/, .git/, vendor/, tests/, root-level README* / LICENSE* / CHANGELOG*, editor scratch, or out-of-tree [bin] paths — the GitHub release tarball doesn’t ship those either):

• stryke.toml (required)
• lib/ subtree (recursive, if present)
• bin/ subtree (recursive, if present)

Packages with [bin] entries pointing outside bin/ are rejected by the release-tarball staging step (every shipped binary lives under bin/<name>.stk); the path install enforces the same rule by simply not copying anything outside the canonical subtrees, so an out-of-tree [bin] path becomes a no-op at install time rather than a store-layout divergence.

Existing destination is removed first so re-installs see fresh content.