Command line/configuration option for choosing registry/registries

[simendsjo]

It would be nice if you could set the registry location at the command line. This makes it possible to use for testing purposes and private repos (good for companies).

Seems like a quick fix, but I'm not sure what you think as you haven't made that option available.

Ref. https://github.com/rejectedsoftware/dub/blob/master/source/app.d#L98

[s-ludwig]

Our idea was to allow specifying a list of URLs in a central configuration file, so that multiple registries can be used in parallel. SSince this would require a bit more effort, it landed on a slot a bit further down road.

[simendsjo]

That is nice, but I was thinking of pointing DUB to another repository. Like a command-switch

--registry "http://mycompany.com/in-house/dub"

[s-ludwig]

Wouldn't that be solved by using

"repositories": [
    "http://mycompany.com/in-house/dub",
    "http://registry.vibed.org"
]

I just think that it would be quite magic knowledge what to pass to the command line and also repeated work if this has to be done for each invocation.

[simendsjo]

Wouldn't that be solved by using
Right. Is the repository listing though to be a dub global, per user, per repository, per dependency..?

[s-ludwig]

I'd say global and per user should be supported. Per package could also be an option, but I'm not sure if this wouldn't case a mess in the end (e.g. that potentially a lot of packages would need to be fixed when a URL changes).

Specifying a specific download URL for a dependency similar to the already supported custom path sounds like it could also be useful, but maybe that can be left for the case that someone actually needs it.