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

What is Paths_app? #343

Closed
chrissound opened this issue Nov 10, 2018 · 2 comments
Closed

What is Paths_app? #343

chrissound opened this issue Nov 10, 2018 · 2 comments

Comments

@chrissound
Copy link

I've just tried to use another local package as a dependency with stack but it seems hpack generates a Paths_app which results in an error of:

Loading stack ghci --ghci-options='-fdiagnostics-color=always' ...
The same package name is used in multiple local packages

app used in:
- PLOther (PLFilePath "/home/chris/Haskell/NiobiumCoconut")
- PLOther (PLFilePath ".")

What is this module doing? Is it possible to exclude to resolve the above error?

@sol
Copy link
Owner

sol commented Nov 10, 2018

Hey! Thanks for reporting this!

hpack generates a Paths_app which results in an error of

I don't see a reference to Paths_app in that error message.

What is this module doing? Is it possible to exclude to resolve the above error?

Paths_* is generated by Cabal (first google hit on the topic http://neilmitchell.blogspot.com/2008/02/adding-data-files-using-cabal.html).

You can prevent hpack from including Paths_* in your package description by specifying other-modules manually (in the simplest case just other-modules: []).

See also #303.

@chrissound
Copy link
Author

Apologies this does not seem to be related to Paths_app or hpack, I assumed the PLOther related to Paths_app - but just seems like verbose error. Thank you for your response! :)

To anyone else that has stumbled upon this:
It's to do with the package name (in my case app) being used in both of the packages.

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

No branches or pull requests

2 participants