Feature Proposal : Fetcher Configuration #996
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The changes in this pull request add preliminary support for configuring the utilities that Spack uses in order to fetch archives from the web. This preliminary support includes the following features:
fetchers.yaml
as the recognized configuration file for Spack fetchers.show_status
configuration option, which can be used to specify whether or not Spack displays a progress bar when downloading archives (useful since the progress bar forcurl
is broken in many environments).I'm hoping to extend this set of configuration options sometime soon to make it possible to configure Spack's default archive fetcher (i.e. adding an option like
fetcher: (curl|wget|...)
). Other configuration options could also be added to solve the problems discussed in #69 and #895.Please let me know if there are any problems with this implementation or any improvements that I can make to it!