On Nov 6, 2012, at 5:01 PM, Frank Shearar <frank.shearar@gmail.com> wrote:
On 6 November 2012 15:56, Chris Muller <asqueaker@gmail.com> wrote:
If SqueakSource would be made read-only even for existing projects, it could help "encourage" the transition to the new resources (ss3 and hub).
I can't speak for others, but I'd personally find that quite irritating (and I make sure I keep my ss3 repos in sync with the ss ones).
what is irritating? having a r/o repository? or having a repository that crashes because is overflowed? keeping in sync both versions unnecessary extra work, IMO. Better to move and clean the project... then you are also collaborating to the stability of the R/O repository (which I agree, should remain online for some time)
But the King still needs to remain available for some time yet -- to preserve some of the diamonds in there which may not have a caretaker at this time.
More than that: Metacello has - as I understand it at least - coupled the notion of a project together with the source of that project. In other words, a ConfigurationOfFoo says "get these packages from this server". That means that unless you take care in how you write your ConfigurationOfs your source location is a single point of failure.
Dale, how complicated would it be to separate out the notion of findability? In other words, to have the person _executing_ the ConfigurationOf to say "look for packages in these locations" with defaults set to {ss. latAm. ss3}?
That's already there. Metacello can say: get this package from this list of possible repositories. Problem is that most of configurations are not aware of that. spec repositories: [ spec repository: 'primary'. spec repository: 'secundary'. spec repository: 'etc...' ]
frank
On Tue, Nov 6, 2012 at 3:45 AM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Hi,
I strongly recommend all of you to move your projects into one of the alternatives:
http://smalltalkhub.com http://ss3.gemstone.com
the king is dead, long live the king!
Esteban