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

Add a --dry-run mode #39

Closed
ericdill opened this issue Mar 1, 2017 · 0 comments

Comments

@ericdill
Copy link
Contributor

@ericdill ericdill commented Mar 1, 2017

As the maintainer of the conda-mirror infrastructure at MaxPoint I want to be able to update my yaml config file and see what is going to happen as a result without actually running the full mirror. A --dry-run flag would be a reasonable way to do this. My thoughts are that enabling this flag would do the following:

  1. Use the target yaml config file to compute the packages that we want to have locally
  2. Compare the contents of the target mirror directory with the packages that we want to have that was computed in (1)
  3. If no verbosity (-v) flags are provided, assume that the user is not interested in exactly what packages are going to be mirrored and show a summary statistic of the number of files that will be downloaded, the total download size and the number of files that will be removed and the total size of packages removed. The package size can be obtained from the "size" key in each packages repodata entry.
  4. If any verbosity flag is provided, show all of the packages that are going to be removed and all of the packages that are going to be downloaded in addition to (3)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.