You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We started an experimental migration of our packages to conan 2.x.
In our integration with conan 1.x we used the following to check the integrity of packages in the local cache based on the manifest:
conan upload --skip-upload --all -c '*'
In conan 2.x --skip-upload is gone, thus the above does not seem to be possible any more.
Question:
Is a local integrity check based on the manifest possible in some other way or is the recommended way to implement a custom command for this?
Perhaps a conan cache check PATTERN sub-command to conan cache would be the right place for such a feature
Have you read the CONTRIBUTING guide?
I've read the CONTRIBUTING guide
The text was updated successfully, but these errors were encountered:
bbandix
changed the title
[question] Local integrity check of cache contents based on manifest
[question] conan2 local integrity check of cache contents based on manifest
Mar 22, 2023
It is true that Conan 2.0 removed this "skip-upload" case that can be leveraged for checking packages checksums.
I think we might want to introduce this check, probably as a conan cache subcommand, labeling this as a possible feature.
In the meantime, it should be relatively easy to create your own custom command to do that, because the api exposes it, something like this could be enough:
What is your question?
Hi!
We started an experimental migration of our packages to conan 2.x.
In our integration with conan 1.x we used the following to check the integrity of packages in the local cache based on the manifest:
conan upload --skip-upload --all -c '*'
In conan 2.x
--skip-upload
is gone, thus the above does not seem to be possible any more.Question:
conan cache check PATTERN
sub-command to conan cache would be the right place for such a featureHave you read the CONTRIBUTING guide?
The text was updated successfully, but these errors were encountered: