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

Collaboration improvements #8

Closed
stefanches7 opened this issue Jul 26, 2018 · 1 comment
Closed

Collaboration improvements #8

stefanches7 opened this issue Jul 26, 2018 · 1 comment

Comments

@stefanches7
Copy link
Collaborator

There is a problem with multiple people working on wBuild projects using version control systems, because the latter updates the modification date on pull.
Example: So say, Elegans updates a script and lets the build run overnight, then pulls it to git; Foraminifer comes tomorrow and pulls the changes, and although the very same script's output is already in the common folder, he has to run the whole build again, because modification date of the updated script is newer!

@stefanches7
Copy link
Collaborator Author

stefanches7 commented Jul 26, 2018

Ideas:

  • Do some version control hack so that mod. date is preserved
  • Use hashsums instead of modification date to check build's consistency

@stefanches7 stefanches7 reopened this Aug 22, 2018
stefanches7 referenced this issue Aug 22, 2018
Closes #7

additional: better document special snakemake rules
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