>Nicolas', I liked change as it allows you to be more concise in >settings while still getting all the benefits, though it does assume a
>1-for-1 proxying of remote repositories in your repository manager, >which is a good practice to follow anyway IMO. If you hit an id that >you haven't accounted for, you'll likely hit a 404 in the repository >manager, which is better than just sending them all to a default route >and hoping they go to central or any other proxies configured. You can >still special case that repository in your settings as you would now, >so nothing is lost. In an Enterprise, I don't like having to rely on all the developers to have all their repo settings done correctly. It's much easier to manage a group of repositories (accessed via a single url) from the proximity side where I have control, I can change the settings and add new repos and have to roll out to an entire organization. That said, Nicolas' change is really an entirely new feature. The current code (and my proposal/patch) are about selecting a defined mirror based on a set of rules. What Nicolas' has is really a transformation of the mirror url that should be done after selection (not mixed in with). I think they can fit together, but it should be well defined and documented if we're adding it. I personally think that the whole mirror section needs to be revisted in 2.1 to add a way to really bind in a repo manager and to allow profiles in the settings to control it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
