-
Notifications
You must be signed in to change notification settings - Fork 75
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
Changelog / as-of request #87
Comments
pypi-timemachine prompted me to think about this kind of thing on repo2docker, and it would be super cool to have something similar for conda, especially if it were an officially supported conda feature and not need a wrapper like pypi-timemachine. For our cases, I don't super care about the changelog part, only the "try to run as if it were date X" part. However you achieve that would be great! It appears that packages have upload timestamps, so adding a condition |
right, in the repodata on conda you do have the timestamp field which would allow you to do this kind of thing today. The timestamp is the upload time though ... but I don't know if there could be a way to add the real version release date as well. |
upload time is what's really relevant for simulating a past install, though, so I think that's fine. |
that is a neat idea. |
Being able to do an install as-of a specified timestamp is an important aspect of reproducibility. xref: mamba-org/conda-specs#3 I thought the timestamp in the I really think storing package specs in a proper database rather than a json file is the way to go - it makes things like filtering the universe of packages on the |
indeed, the timestamps in package's we may add the upload time query to quetz api, which would make the as-of/changelog feature relatively easy to implement, but this would break compatibility with anaconda server. Should we go for it? |
+:100: from me! I don't think it breaks compatibility - certainly no more than does |
Having a changelog for conda channels may have many benefits
The text was updated successfully, but these errors were encountered: