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

Question: is the config field archive-mirrors respected? #5272

Closed
hannesm opened this issue Sep 3, 2022 · 3 comments
Closed

Question: is the config field archive-mirrors respected? #5272

hannesm opened this issue Sep 3, 2022 · 3 comments

Comments

@hannesm
Copy link
Member

hannesm commented Sep 3, 2022

Hello,

in the manual I read that you can set archive-mirrors: [ "<URL>" ... ] in the opam configuration file. Now, setting it in ~/.opam/config doesn't seem to have any effect -- tarballs are still downloaded from opam.ocaml.org.

My test case was opam source <package>. I'm using opam 2.1.2.

Thanks for developing opam and have a nice weekend!

@hannesm
Copy link
Member Author

hannesm commented Sep 3, 2022

NB: there's a separate repofiled archive-mirrors (as part of the repo file), but I'm asking about #configfield-archive-mirrors.

@dra27
Copy link
Member

dra27 commented Sep 5, 2022

The website has too up-to-date documentation (it's display docs from opam master rather than latest stable release!). See also #4411 which has been fixed in #4830 which will be in 2.2 - so if you're happy to try opam master, this should be working (and please do re-open if that turns out not to be the case)

@dra27 dra27 closed this as completed Sep 5, 2022
@hannesm
Copy link
Member Author

hannesm commented Sep 5, 2022

Dear @dra27, thanks for your quick response. Maybe it would be worth to state in the documentation kind of "since 2.2.0" or similar then? Yes, I understand that this feature has been present for longer, but #4411 explains pretty well the confusion...

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

2 participants