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

caching flags? #3156

Closed
mwotton opened this issue May 3, 2017 · 3 comments
Closed

caching flags? #3156

mwotton opened this issue May 3, 2017 · 3 comments

Comments

@mwotton
Copy link

mwotton commented May 3, 2017

this is more a general question - is there a strong reason not to include a hash of the flags (and other relevant configuration) in the cache directory? it's kind of annoying that running a profiling build means rebuilding everything, or adopting a filthy hack like http://www.shimweasel.com/2017/04/27/haskell-profiling-without-pain

even nix doesn't solve this problem for the actual build as far as I'm aware, only for dependencies. Is this something the stack devs think is worth solving? should it be done by another tool?

@mwotton
Copy link
Author

mwotton commented May 3, 2017

alternatively, if there's a way to dump all the things stack uses to decide whether something is dirty or not, i'm happy to roll a wrapper script.

@bitemyapp
Copy link
Contributor

#2957 possibly relevant?

@mgsloan
Copy link
Contributor

mgsloan commented Aug 7, 2017

Yup, I've certainly been frustrated with that too at times @mwotton . I've added a comment to #2684 , closing this ticket as a duplicate of that

@mgsloan mgsloan closed this as completed Aug 7, 2017
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

3 participants