Skip to content
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

Local extra-dep executable overwritten by project package executable, without warning #6504

Open
mpilgrem opened this issue Mar 2, 2024 · 0 comments

Comments

@mpilgrem
Copy link
Member

mpilgrem commented Mar 2, 2024

It appears that:

  • built executables of a local extra-dep are installed in the install\<hash>\bin directory of the project's Stack work directory; and
  • built executables of a project package are installed in the same directory.

In the case of project packages with executables with the same name, Stack issues a warning. That is handled by Stack.Build.warnIfExecutablesWithSameNameCouldBeOverwritten (following resolution of #1198). However, no warning is triggered if the clash involves a local extra-dep's executable.

stack --version
Version 2.16.0, Git revision 2adc11c27bdaa6a49b1cfeeebb1299710f865185 (dirty) (10623 commits) PRE-RELEASE x86_64
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant