Re: [Pharo-project] Universes and Installer?
It makes a lot of sense to use MC, universes, etc. rather than re-write them; no argument there. Would it help to roll ScriptLoader into Installer? Installer _looks_ to me as though it tries to be a much-needed facade over the various options for sharing code. The problem is complex, so must be the solution, but I think it would help to have a single entry point even if it is merely a facade. Bill aka Confused Smalltalker :) Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab@anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029
alexandre@bergel.eu 12/22/08 10:39 AM >>> Works. Thanks!
Alexandre On 22 Dec 2008, at 12:26, Damien Cassou wrote:
On Mon, Dec 22, 2008 at 4:18 PM, Alexandre Bergel <Alexandre.Bergel@inria.fr> wrote:
If I execute "Installer universe" in a workspace, an error "Universes code not present" is signaled . Does this mean that only a subset of Installer is present in Pharo- Core?
No, you have the complete Installer package. However, Installer needs some back-ends. Depending on what you want to, you will need SqueakMap, Monticello, Sake and Universes.
On the Installer squeaksource repository there is a package Universes. It looks like to be the right candidate. However, some extensions on StringSocket need to be present. I do not know where to get them from.
You could use the dev images but I guess you won't do it. So, just execute:
ScriptLoader new installingUniverse
http://www.squeaksource.com/Installer.html does not say much on this. Keith? Do I miss something?
-- Damien Cassou http://damiencassou.seasidehosting.st
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Bill Schwab wrote:
It makes a lot of sense to use MC, universes, etc. rather than re-write them; no argument there. Would it help to roll ScriptLoader into Installer? Installer works for all commonly used Squeak images, so you would need a ScriptLoader for each image that people are using.
Coincidentally that is almost exactly the way Sake/Packages already works, except that it is aware of dependencies and can sort a list of items that it is asked to load in order to honour dependencies. The functions that ScriptLoader performs should really be rolled into the Packages-Library class PacakgesPharo01, for Sake/Packages which is a repository of "scripts" for loading things (most definitions simply supply a url rather than a script). Installer should be loaded using one of the maintained bootstrap methods, rather than via ScriptLoader. i.e LevelPlayingField. However if you dont want to do that the maintained bootstrap for installer only is: HTTPSocket httpFileIn: 'installer.pbwiki.com/f/Installer.st'. followed by Installer upgrade. Once you have Installer loaded, it can access squeakmap using the web interface, so it doesnt actually need SqueakMap to be loaded to begin bootstrapping other things e.g. Installer websqueakmap install: 'Whatever'. Finally you can put your scripts on a web page somewhere, or use installer.pbwiki.com to provide a simple script that works like so: Installer install: 'SomeScript'.
problem is complex, so must be the solution, but I think it would help to have a single entry point even if it is merely a facade.
The single entry point for Installer is supposed to be LevelPlayingField, which ensures that Installer has everything it needs to load from Monticello repositories, mantis, urls, and websqueakmap. Followed by Sake/Packages which knows about everything else. (which is very easy to remove once you are done building). Keith
On Dec 22, 2008, at 17:47 , Keith Hodges wrote:
Bill Schwab wrote:
It makes a lot of sense to use MC, universes, etc. rather than re- write them; no argument there. Would it help to roll ScriptLoader into Installer? Installer works for all commonly used Squeak images, so you would need a ScriptLoader for each image that people are using.
Coincidentally that is almost exactly the way Sake/Packages already works, except that it is aware of dependencies and can sort a list of items that it is asked to load in order to honour dependencies. The functions that ScriptLoader performs should really be rolled into the Packages-Library class PacakgesPharo01, for Sake/Packages which is a repository of "scripts" for loading things (most definitions simply supply a url rather than a script).
uh, sure? The main purpose of ScriptLoader is to support the generation of new updates. I recently implemented support for almost the complete process from detecting new changes, simulate the update for testing, pushing changes to SqueakSource and generating the scripts and cs files for the update stream. People started adding #loadOB methods on the class side of ScriptLoader -- I guess, these may be better handled by Sake/Packages. Adrian
Scriptloader is our internal code to publish release. It is not for public consumption. It works well but only for us. For the rest we should Installer and I'm waiting damien to write some text on Sake and Packages so that I finally understand them. Stef On Dec 22, 2008, at 5:09 PM, Bill Schwab wrote:
It makes a lot of sense to use MC, universes, etc. rather than re- write them; no argument there. Would it help to roll ScriptLoader into Installer? Installer _looks_ to me as though it tries to be a much-needed facade over the various options for sharing code. The problem is complex, so must be the solution, but I think it would help to have a single entry point even if it is merely a facade.
Bill aka Confused Smalltalker :)
Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254
Email: bschwab@anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029
alexandre@bergel.eu 12/22/08 10:39 AM >>> Works. Thanks!
Alexandre
On 22 Dec 2008, at 12:26, Damien Cassou wrote:
On Mon, Dec 22, 2008 at 4:18 PM, Alexandre Bergel <Alexandre.Bergel@inria.fr> wrote:
If I execute "Installer universe" in a workspace, an error "Universes code not present" is signaled . Does this mean that only a subset of Installer is present in Pharo- Core?
No, you have the complete Installer package. However, Installer needs some back-ends. Depending on what you want to, you will need SqueakMap, Monticello, Sake and Universes.
On the Installer squeaksource repository there is a package Universes. It looks like to be the right candidate. However, some extensions on StringSocket need to be present. I do not know where to get them from.
You could use the dev images but I guess you won't do it. So, just execute:
ScriptLoader new installingUniverse
http://www.squeaksource.com/Installer.html does not say much on this. Keith? Do I miss something?
-- Damien Cassou http://damiencassou.seasidehosting.st
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (4)
-
Adrian Lienhard -
Bill Schwab -
Keith Hodges -
Stéphane Ducasse