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

Request: More flexible checking? #165

Open
kendonB opened this issue Apr 12, 2017 · 0 comments
Open

Request: More flexible checking? #165

kendonB opened this issue Apr 12, 2017 · 0 comments

Comments

@kendonB
Copy link

kendonB commented Apr 12, 2017

As far as I can tell, the current checking options do the following:

  • exists checks the target exists and builds if not
  • code is exists + checks the target generating code and builds if it changed
  • depends is exists + checks ALL the target's dependencies with md5's and builds if one or more has changed

I have a target where a bunch of the dependencies are raw data that will never change, but two dependencies come from earlier code that might change. Computing the md5's on the raw data is expensive, but that seems like the only way to get remake to check the two earlier-code-dependent dependencies.

Perhaps adding check: specific_dependency_name to the API could work? Or is there a way to do this now?

Hope this helps. Great package!

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

1 participant