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
pub global activate already supports hosted, path, and git sources, but the hosted option defaults to the main pub server with no way to activate from a separate server. We have a private pub server for our internal packages and it would be nice to be able to globally activate some of them using the standard version constraints.
It looks like this idea was at least considered previously in this issue: #1044
pub global activate foo ">=1.0 <2.0" --server http://...
Is there any reason not to support this? And if not, would it be something that you would accept a PR for? Looking at the implementation of the global activate command, it looks like it might require a separate cache for each pub server, but otherwise seems to be straightforward.
The text was updated successfully, but these errors were encountered:
pub global activate
already supports hosted, path, and git sources, but thehosted
option defaults to the main pub server with no way to activate from a separate server. We have a private pub server for our internal packages and it would be nice to be able to globally activate some of them using the standard version constraints.It looks like this idea was at least considered previously in this issue: #1044
Is there any reason not to support this? And if not, would it be something that you would accept a PR for? Looking at the implementation of the global activate command, it looks like it might require a separate cache for each pub server, but otherwise seems to be straightforward.
The text was updated successfully, but these errors were encountered: