You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 20, 2023. It is now read-only.
The branch mk-src-ent has made a big push on this, and aims to create a formal spec for pkgEnt. This will help land on a common standard for package definitions to be shared in overlays across projects.
While pkgSet pipelines necessarily need to be more flexible, a set of interfaces implemented by different backends should help scaling small clusters centered around package locks and workspaces to be compatible with larger hierarchical sets with multiple versions like we have in flocoPackages.
addFlocoPackage[s] ( overlay generator ), getFlocoPackage ( lookup by exact ident+version ), resolveFlocoPackages ( filters by semver ), and similar interfaces can abstract a packument VInfo hierarchy vs. a keyed set. Definitions for these already exist for the keyed metaSet backend.
The text was updated successfully, but these errors were encountered:
The branch
mk-src-ent
has made a big push on this, and aims to create a formal spec forpkgEnt
. This will help land on a common standard for package definitions to be shared in overlays across projects.While
pkgSet
pipelines necessarily need to be more flexible, a set of interfaces implemented by different backends should help scaling small clusters centered around package locks and workspaces to be compatible with larger hierarchical sets with multiple versions like we have inflocoPackages
.addFlocoPackage[s]
( overlay generator ),getFlocoPackage
( lookup by exact ident+version ),resolveFlocoPackages
( filters by semver ), and similar interfaces can abstract a packument VInfo hierarchy vs. a keyed set. Definitions for these already exist for the keyedmetaSet
backend.The text was updated successfully, but these errors were encountered: