Skip to content

Pass the precompile flag through to the backend installer - #623

Merged
ugexe merged 1 commit into
mainfrom
ugexe/forward-precompile-install
Sep 17, 2026
Merged

ugexe merged 1 commit into
mainfrom
ugexe/forward-precompile-install

Conversation

@ugexe

@ugexe ugexe commented Aug 16, 2026

Copy link
Copy Markdown
Owner

Previously Zef::Install.install accepted a :$precompile named argument but never forwarded it, so the backend installer always received an undefined Bool and CompUnit::Repository::Installation.install skipped precompilation entirely. As such nothing installed to an unnamed repository, e.g. --to=inst#/some/path, has been precompiled since 5d4cf5b. Installs to a named repository like site were unaffected because the staging workflow calls .install on the staging repository directly rather than going through this code path.

This forwards the argument and defaults :$precompile to True on both install methods, so leaving it unspecified precompiles as the documentation already describes.

Previously `Zef::Install.install` accepted a `:$precompile` named argument
but never forwarded it, so the backend installer always received an
undefined `Bool` and `CompUnit::Repository::Installation.install` skipped
precompilation entirely. As such nothing installed to an unnamed repository,
e.g. `--to=inst#/some/path`, has been precompiled since 5d4cf5b. Installs to
a named repository like `site` were unaffected because the staging workflow
calls `.install` on the staging repository directly rather than going
through this code path.

This forwards the argument and defaults `:$precompile` to `True` on both
`install` methods, so leaving it unspecified precompiles as the
documentation already describes.
@ugexe
ugexe merged commit f432466 into main Sep 17, 2026
6 checks passed
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