Skip to content

Offer to re-use previously built packages when installing#249

Open
intentionally-left-nil wants to merge 1 commit intovn971:masterfrom
intentionally-left-nil:use-checked-packages-for-upstream
Open

Offer to re-use previously built packages when installing#249
intentionally-left-nil wants to merge 1 commit intovn971:masterfrom
intentionally-left-nil:use-checked-packages-for-upstream

Conversation

@intentionally-left-nil
Copy link

Installing or updating a package causes the package to be rebuilt every time. In the case where multiple packages are installed or updated at once, any singular reason for failure causes all packages to be rebuilt on subsequent install or update commands.

This commit detects that a package was already built and verified by the user, and offers to use the previously-built package instead of rebuilding it.

In order to prevent out-of-date packages from being used, the commit also ties the package to the git SHA of the build recipe. Any updates or changes will cause the package to be rebuilt.

This behavior is presented as a choice to the user. For any package where a cached package is available, the user chooses whether to rebuild it or used the cached version. This choice is per-package. Choosing rebuilding persists the existing behavior, and choosing the cached option skips the build and verify steps of the installation process

@intentionally-left-nil
Copy link
Author

I needed to rebase this a little bit to work with the other PR's I've opened, we can use intentionally-left-nil#5 if the previous PR's are accepted first

Installing or updating a package causes the package to be rebuilt every
time. In the case where multiple packages are installed or updated at
once, any singular reason for failure causes all packages to be rebuilt
on subsequent install or update commands.

This commit detects that a package was already built and verified by the
user, and offers to use the previously-built package instead of
rebuilding it.

In order to prevent out-of-date packages from being used, the commit
also ties the package to the git SHA of the build recipe. Any updates or
changes will cause the package to be rebuilt.

This behavior is presented as a choice to the user. For any package
where a cached package is available, the user chooses whether to rebuild
it or used the cached version. This choice is per-package. Choosing
rebuilding persists the existing behavior, and choosing the cached
option skips the build and verify steps of the installation process
@intentionally-left-nil intentionally-left-nil force-pushed the use-checked-packages-for-upstream branch from 0d77b11 to 515463c Compare February 23, 2026 22:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant