[Pharo-project] Let's get rid of Core vs. Full

Stéphane Ducasse stephane.ducasse at inria.fr
Tue Apr 5 20:50:07 CEST 2011


On Apr 5, 2011, at 3:00 AM, Hernán Morales Durand wrote:

> Please someone clarify, are you going to kill the core?
> 
> Honestly I don't know how people survive with the dev image, I guess
> you have super fast laptops.

But you can unload packages.

> 
> Not my case, and the Core just run nice in "old" hardware.
> 
> 2011/4/4 Germán Arduino <garduino at gmail.com>:
>> As I can understand the proposal of Marcus is not have anymore an
>> image without the minimal set of tools for development. And I full
>> agree with this option.
>> 
>> Allways is possible to shrink the image in a next step if needed. In
>> other words, to me Core is not useful witthout a minimal set of dev
>> tools and I'm doing production deployments with such tools with no
>> problems. By other hand, as most of the images are in remote servers I
>> need to use them via VNC and with the dev tools.
>> 
>> Just my opinion.
>> 
>> Cheers.
>> 
>> 
>> 2011/4/4 Tudor Girba <tudor.girba at gmail.com>:
>>> This is what I understood from what Marcus said, too :)
>>> 
>>> Cheers,
>>> Doru
>>> 
>>> 
>>> On 4 Apr 2011, at 15:57, Stéphane Ducasse wrote:
>>> 
>>>> This is my ideas.
>>>> 
>>>>> My proposition for 1.3:
>>>>> 1) Add MetacelloBrowser and switch to version-separated repositories (like MetaRepoForPharo11, etc. -I don't like the "abbreviated names" but you get the idea)
>>>>> 2) Reduce the "full" image to Core+OB+RB+Shout+OCompletion+Finder+MetacelloBrowser
>>>>> 3) If it is possible, develop Core image into this reduced full image.
>>>> 
>>>> 
>>> 
>>> --
>>> www.tudorgirba.com
>>> 
>>> "Every thing should have the right to be different."
>>> 
>> 
>> 
> 
> 
> 
> -- 
> Hernán Morales
> Information Technology Manager,
> Institute of Veterinary Genetics.
> National Scientific and Technical Research Council (CONICET).
> La Plata (1900), Buenos Aires, Argentina.
> Telephone: +54 (0221) 421-1799.
> Internal: 422
> Fax: 425-7980 or 421-1799.
> 




More information about the Pharo-project mailing list