[Pharo-project] now that squeaksource is back...
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
On 11/6/12 7: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
Yesterday I start using http://ss3.gemstone.com. Could comment about advantages (or not) of using smalltalkhub.com ? And very thanks.. Edgar
If SqueakSource would be made read-only even for existing projects, it could help "encourage" the transition to the new resources (ss3 and hub). 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. 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
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).
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}? 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
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
On 6 November 2012 16:10, Esteban Lorenzano <estebanlm@gmail.com> wrote:
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)
Yes. It means that I _cannot_ keep the repositories in sync, which means that someone might well not be able to load ConfigurationOfControl correctly.
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...' ]
That's not what I meant. I want the author to say "this piece of software contains these parts, and these are the canonical locations", and the user should be able to completely override those locations. frank
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
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...' ]
That's not what I meant. I want the author to say "this piece of software contains these parts, and these are the canonical locations", and the user should be able to completely override those locations.
#repositoryOverrides: self whateverVersion repositoryOverrides: (self whateverRepo); load
frank
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
-- Mariano http://marianopeck.wordpress.com
On 6 November 2012 16:55, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
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...' ]
That's not what I meant. I want the author to say "this piece of software contains these parts, and these are the canonical locations", and the user should be able to completely override those locations.
#repositoryOverrides:
self whateverVersion repositoryOverrides: (self whateverRepo); load
I have actually tried to do these things. repositoryOverrides: is _insufficient_. It doesn't protect you from a transitive dependency's repository not being available. frank
frank
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
-- Mariano http://marianopeck.wordpress.com
Frank Shearar-3 wrote
On 6 November 2012 16:55, Mariano Martinez Peck <
marianopeck@
> wrote:
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...' ]
That's not what I meant. I want the author to say "this piece of software contains these parts, and these are the canonical locations", and the user should be able to completely override those locations.
#repositoryOverrides:
self whateverVersion repositoryOverrides: (self whateverRepo); load
I have actually tried to do these things. repositoryOverrides: is _insufficient_. It doesn't protect you from a transitive dependency's repository not being available.
frank
I created a solution that may do what you want on Pharo or be a start for what you have in mind here: http://code.google.com/p/metacello/issues/detail?id=182 The code in that changeset detects whether Squeaksource is down when loading a project and then load it and its dependencies from the Chilean mirror if Squeaksource is down. It only replaces the squeaksource repos with chilean repos during each run of the loading process rather than editing the project's configs. It does that for the project you want to load and all its dependent projects and packages. And their dependenices. It allowed me to load Seaside 3.0.7 into a fresh Pharo 1.4 image from Chile when squeaksource was down yesterday. The issue I ran into on Squeak 4.3 is that the error MCHttpRepository>>#allFileNames creates when it cannot access the repos on Squeaksource stops the loading process. -- View this message in context: http://forum.world.st/now-that-squeaksource-is-back-tp4654045p4654207.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Frank, With the Metacello Scripting API, I have introduced just the capability you are looking for. You can specify that a particular project be associated with a particular repository location for your image and whenever that project is referenced your "local override" will be used ... I haven't released this feature yet, because I'm looking for more feedback on the API. I was hoping that I would get experience reports from Pharo2.0 users, but the Metacello Scripting API doesn't work on Pharo2.0 (lack of OSProcess support) so I have backed off on the pedal for trying to push both the Scripting API and git support into production ... If you want to take the Preview release for a spin (and aren't using Pharo2.0) let me know. Dale ----- Original Message ----- | From: "Frank Shearar" <frank.shearar@gmail.com> | To: "ma chris m" <ma.chris.m@gmail.com>, "The general-purpose Squeak developers list" | <squeak-dev@lists.squeakfoundation.org> | Cc: Pharo-project@lists.gforge.inria.fr | Sent: Tuesday, November 6, 2012 8:01:07 AM | Subject: Re: [squeak-dev] Re: [Pharo-project] now that squeaksource is back... | | 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). | | > 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}? | | 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 | > | |
On Tue, Nov 06, 2012 at 10:45:57AM +0100, Esteban Lorenzano wrote:
Hi,
I strongly recommend all of you to move your projects into one of the alternatives:
I would appreciate some guidance as to which of these is intended to serve as the long term replacement for SqueakSource, and how specifically I should go about migrating an existing project from SqueakSource to the replacement system. Thanks, Dave
On 6 November 2012 17:29, David T. Lewis <lewis@mail.msen.com> wrote:
On Tue, Nov 06, 2012 at 10:45:57AM +0100, Esteban Lorenzano wrote:
Hi,
I strongly recommend all of you to move your projects into one of the alternatives:
I would appreciate some guidance as to which of these is intended to serve as the long term replacement for SqueakSource, and how specifically I should go about migrating an existing project from SqueakSource to the replacement system.
Dave, Mariano's written up something which ought to help: http://marianopeck.wordpress.com/2011/11/08/migrating-projects-to-squeaksour... (I use ss3 for my new projects (but I'd rather be using GitHub).) frank
Thanks, Dave
you can find Gofer scripts in the Gofer chapter. Stef
Hi,
I strongly recommend all of you to move your projects into one of the alternatives:
I would appreciate some guidance as to which of these is intended to serve as the long term replacement for SqueakSource, and how specifically I should go about migrating an existing project from SqueakSource to the replacement system.
Thanks, Dave
participants (9)
-
Chris Muller -
Dale Henrichs -
David T. Lewis -
Edgar J. De Cleene -
Esteban Lorenzano -
Frank Shearar -
Mariano Martinez Peck -
Paul DeBruicker -
Stéphane Ducasse