Any objection to including Gofer in a near-future Squeak?
El mar, 26-01-2010 a las 14:48 -0800, Randal L. Schwartz escribió:
Any objection to including Gofer in a near-future Squeak?
It is MIT, you can do what you want with it :)
Of course is the point of the squeak vs. pharo... but technically and legally, you can, it is your (the people/the board/the community/not randal's) Squeak. :)
On Tue, 26 Jan 2010, Randal L. Schwartz wrote:
Any objection to including Gofer in a near-future Squeak?
1. It relies on Monticello which is different in Squeak and Pharo (and the difference will probably grow, since Pharo may drop mcd support in the future (http://lists.gforge.inria.fr/pipermail/pharo-project/2010-January/021074.htm... )) 2. Do we really need it in Squeak, can't it just be a loadable package?
Levente
-- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 merlyn@stonehenge.com URL:http://www.stonehenge.com/merlyn/ Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
Sounds to me like it would be better to make MC1.6 loadable in trunk from squeaksource/mc, then add the necessary gofer functionality to MC (if even needed).
Ken G. Brown
Randal L. Schwartz wrote:
Any objection to including Gofer in a near-future Squeak?
I noticed yr question about MetaCello and Gofer (in SmallWiki):
Randal said: " So this is my first time using MetaCello, and it looks like to bootstrap it from Squeak Trunk, I have to go into the Monticello Browser GUI, and pick the latest package of ConfigurationOfMetacello manually. Is there any way to automate all of this in some sort of "doit"? "
I just wanted to say that you could do from trunk now:
squeaksource := Installer repository: 'http://www.squeaksource.com'. mcrp := squeaksource project: 'MetacelloRepository'. mcrp install: 'ConfigurationOfMetacello'. (Smalltalk at: #ConfigurationOfMetacello) perform: #loadLatestVersion
- Jeroen
On Wed, 27 Jan 2010, Jeroen van Hilst wrote:
Randal L. Schwartz wrote:
Any objection to including Gofer in a near-future Squeak?
I noticed yr question about MetaCello and Gofer (in SmallWiki):
Randal said: " So this is my first time using MetaCello, and it looks like to bootstrap it from Squeak Trunk, I have to go into the Monticello Browser GUI, and pick the latest package of ConfigurationOfMetacello manually. Is there any way to automate all of this in some sort of "doit"? "
I just wanted to say that you could do from trunk now:
squeaksource := Installer repository: 'http://www.squeaksource.com'. mcrp := squeaksource project: 'MetacelloRepository'. mcrp install: 'ConfigurationOfMetacello'. (Smalltalk at: #ConfigurationOfMetacello) perform: #loadLatestVersion
Or just (Installer ss project: 'MetacelloRepository') install: 'ConfigurationOfMetacello'. (Smalltalk at: #ConfigurationOfMetacello) perform: #loadLatestVersion.
Levente
- Jeroen
On 27 Jan 2010, at 02:31, Andreas Raab wrote:
Randal L. Schwartz wrote:
Any objection to including Gofer in a near-future Squeak?
Do you mean including Gofer or Metacello? (I.e., is the question really just about Gofer or is it in the context of supporting Metacello?)
When you have a tool for bootstrapping things easily into a basic image, you don't need to have them loaded.
Metacello and Gofer can have bootstrapping scripts added to InstallerScripts, so that
Installer install: 'Gofer'. Installer install: 'Metacello'.
Works in Squeak and Pharo etc.
Installer is designed so that it can be your only dependency so you don't need to have everything and the kitchen sink loaded. It doesn't even need Monticello, since it knows how to install source from inside a mcz.
regards
Keith
squeak-dev@lists.squeakfoundation.org
-
Andreas Raab -
Jeroen van Hilst -
keith -
Ken G. Brown -
Levente Uzonyi -
merlyn＠stonehenge.com -
Miguel Enrique Cobá Martinez