[Pharo-project] latam mirror down?
dhenrich at vmware.com
Wed Sep 5 16:52:07 EDT 2012
----- Original Message -----
| From: "Frank Shearar" <frank.shearar at gmail.com>
| To: Pharo-project at lists.gforge.inria.fr
| Sent: Wednesday, September 5, 2012 1:41:00 PM
| Subject: Re: [Pharo-project] latam mirror down?
| On 5 September 2012 19:18, Dale Henrichs <dhenrich at vmware.com> wrote:
| > Frank,
| > overrideRepositories: overrides all of the repositories used during
| > the load ... it was primarily intended to be used by folks wanting
| > to isolate their development environment from the turbulent
| > internets .... it is not quite as useful for trying to switch
| > between multiple mirrors, you have to provide a complete set of
| > repositories that are up and contain the packages ...
| Do you mean that Metacello will choose, for an entire load, a
| repository? I'd imagined that it would, for each load of each
| try the repositories in order. But if it's per entire load, then
| need each repo-containing server to have the full set of packages.
| That would be more awkward.
Metacello will choose from the entire list of repositories ... Metacello uses Gofer and Gofer does not scan in order...
Supplying multiple repositories will kinda work, but as I said, the overrideRepositories feature was not intended as a solution for repositories going off-line.
| > Each project can specify primary and mirror repositories in their
| > own configuration.
| Yes, which is the problem: how many ConfigurationOfs out there say
| "SS, but fall back to LatAM", or "use the canonical, but fall back to
| SS"? I know _yours_ do, but I suspect most won't.
| > Of course the problem comes up when the mirror repository is down,
| > or the project is only hosted on one repository...
| If a package is hosted on SS, it will be on LatAm too, so all
| SS-hosted packages can now come from either.
This is the desired effect, methinks.
More information about the Pharo-dev