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

Allow Registry.{add,update}() to target specific depots #3088

Merged
merged 2 commits into from
May 20, 2022

Conversation

staticfloat
Copy link
Member

Matching many other Pkg functions, we allow update() here to operate
on a custom set of depots, and add() to operate on a single specificed
depot. This is useful for manipulating registries inside of depots that
are not currently on the DEPOT_PATH.

@staticfloat
Copy link
Member Author

Review with the whitespace filter on; I indented a function so it looks like a giant change.

@staticfloat staticfloat requested a review from KristofferC May 19, 2022 13:08
@staticfloat staticfloat force-pushed the sf/add_update_depot_kwarg branch from 9a25c1a to 5016536 Compare May 19, 2022 13:56
Matching many other `Pkg` functions, we allow `update()` here to operate
on a custom set of depots, and `add()` to operate on a single specificed
depot.  This is useful for manipulating registries inside of depots that
are not currently on the `DEPOT_PATH`.
@DilumAluthge DilumAluthge force-pushed the sf/add_update_depot_kwarg branch from 5016536 to f77a4d7 Compare May 19, 2022 19:25
@KristofferC
Copy link
Member

KristofferC commented May 19, 2022

The other way is of course to do the DEPOT_PATH juggling yourself but this is most likely nicer.

@staticfloat
Copy link
Member Author

Yeah, I thought about that, but I'm always wary of manipulating global variables, because I just know someone is going to try and manipulate two depots in two different tasks.

@staticfloat staticfloat merged commit 610c768 into master May 20, 2022
@staticfloat staticfloat deleted the sf/add_update_depot_kwarg branch May 20, 2022 04:28
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

Successfully merging this pull request may close these issues.

2 participants