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
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 | > | |
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.
Making the original SqueakSource read-only has no bearing on this use-case.
On Tue, Nov 20, 2012 at 10:49 AM, Chris Muller asqueaker@gmail.com wrote:
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.
Making the original SqueakSource read-only has no bearing on this use-case.
Oops, I'm wrong about that. Please disregard.
squeak-dev@lists.squeakfoundation.org
-
Chris Muller -
Dale Henrichs -
Frank Shearar