----- Original Message ----- | From: "Frank Shearar" <frank.shearar@gmail.com> | To: Pharo-project@lists.gforge.inria.fr | Sent: Wednesday, August 22, 2012 11:56:12 AM | Subject: Re: [Pharo-project] latam mirror down? | | On 22 August 2012 19:33, Dale Henrichs <dhenrich@vmware.com> wrote: | > Frank, | > | > You can already do this in your configuration by supplying a list | > of repositories instead of a single repository: | > | > spec | > repository: 'http://seaside.gemstone.com/ss/metacello'; | > repository: 'http://www.squeaksource.com/metacello'. | > | > Gofer is used to do the loads in Metacello, so I don't think that | > Gofer necessarily processes repositories in order , but this is | > the technique I use to insulate Metacello loads from repository | > outages... | | Sure, but I can't do that for ConfigurationOfFFI, for example. I | can't | do that for ObjectsAsMethodWrappers, to talk about what's currently | causing our builds to fail. | | > My latam hack for travis ci had to do with compensating for | > configurations that are "single sourced"... | | Sure, and the presence of the latam mirror _ought_ to mean that any | single-sourced thing on SS would no longer be single source. Surely | it | would be easier all round if travisCI.st (if I remember the name | correctly) defined where to find these packages? (I can hear Chris & | Chris saying "it should look on SM") | | I'll see if I can't hack up something we can pick over. Frank, If you're talking about what I did in builderCI ... then I agree wholeheartedly that a failover of some sort is called for when trying to bootstrap the latam mirror support ... squeaksource was dead at the time and I was in a hurry ... (haven't we heard that before) ... I'd welcome improvements there.... A fail-over scheme for FFI or any arbitrary projects (is that what you're getting at?) is a bit more difficult, but I'd definitely be interested in seeing what you're thinking ... Dale