Skip to content

cabal: Add necessary aliases for vendored packages with executables #2309

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

iteratee
Copy link
Contributor

This allows vendoring of packages with necessary tools from a stack snapshot. For example, if the cabal file for cpphs hasn't yet been bumped on hackage with increased bounds for the newest ghc.

This allows vendoring of packages with necessary tools from a stack
snapshot. For example, if the cabal file for `cpphs` hasn't yet been
bumped on hackage with increased bounds for the newest ghc.
@iteratee iteratee requested a review from avdv as a code owner May 15, 2025 23:25
Copy link
Member

@avdv avdv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

It took me a while to figure out what's going on; so for posterity and to remind myself:

For stack_snapshot there will be a repository called stackage (let's say) and for each of the library components there will be a haskell_cabal_library target.

For exe components, there will be a haskell_cabal_binary target (called _<name>_exe_<exe-name>). But also, there will be an alias (just exe-name) in the stackage-exe repository pointing to the actual haskell_cabal_binary in stackage.

For vendored packages, the haskell_binary_target does not exist in stackage, so this needs another alias pointing to the actual exe target in the repository of the vendored package.

@avdv
Copy link
Member

avdv commented Jun 23, 2025

@iteratee somehow CI failed and I cannot seem to retry it. Could you please rebase and re-push your branch?

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.

2 participants