Adrian Lienhard wrote:
> On Mar 2, 2009, at 09:00 , Stéphane Ducasse wrote:
> 
>> This reminds me some thoughts about time and date.
>>
>> Originally date and time were ok but not so great.
>> Then one guy (brent) fixed it and people were happy and it was
>> introduced in the base system.
>> At that time when time was introduced (in 3.7 I guess) it was a
>> obvious choice.
>> Then chronos and aconcagua went out showing some other properties.
>>
>> Now retrospectively I think that it would be better to have a minimal
>> version in the system and
>> loadable external package. There are some exceptions to this strategy:
>> announcements and regexp
>> (where this is more a language decision), but in general this is a
>> good strategy
> 
> I think a good rule of thumb is whether the code is used by the  
> kernel. Having packages like Regex and Announcements in the core makes  
> only sense if they are also used in the core. Else they would better  
> be external packages.


Then why not structure the packages in 3 parts:

core- All needed to bootstrap a minimal image (kernel, packages to 
install more packages, logging, scripting,etc)

base- All the packages that have various versions but the included one 
is the prefered, suggested, standarized to (Announcements, SUnit, etc)

universes/distros/monticellos/squeaksources- all the packages existing 
and *easily* loadable by the users

Then, with a core image, and a script, you can create a base image.
With a base image and a script or a GUI, you can create your very own 
image (e.g. Damien Cassou's images)

Regards,
Miguel Cobá
> 
> Not sure about median, though, as for just one method you wouldn't  
> want to create and load an extra package...
> 
> Adrian
> 
>>
>> So we could rename median naiveMedian and have a package that does all
>> the rest and
>> that people can load it.
>>
>> Stef
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [email protected]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 
> 
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to