[Pharo-dev] Build process of Pharo image
hilaire.fernandes at gmail.com
Sun Apr 6 06:10:25 EDT 2014
Le 06/04/2014 10:44, Pharo4Stef a écrit :
> On 05 Apr 2014, at 21:48, Hilaire Fernandes <hilaire.fernandes at gmail.com> wrote:
>> Still, I do not get why the newer packages are not loadable with
>> configurations instead of been carved in the image. Why can't packages
>> developers provide such configurations?
> sure give us a list?
> - RB
> - Nautilus
> - spec
> - Keychain
> - key mapping
> - smart suggestions
> - …..
> - and many more
I can give you all the Monticello package list, but is it relevant? I
hardly know 10% of them. Some should probably belong to core other not.
> do you want an image by default without any tools? I do but we need time.
I don't understand: with times new important tools were developed, like
Nautilus and other I don't know I guess. Was it decided these tools
should be carved in the image or be loaded? Was not removing old tools
and using new loadable ones the way to build step by step this core image?
I confess I very likely don't see the subtle details.
> so you are right we are concious about it but no resources.
Is it really a resource problem?
With my scarce resources and knowledge I can build automatically drgeo
with a bash script and a .st file since 1.x for several platform. I
agree it is more complex with Pharo but...
Dr. Geo http://drgeo.eu
More information about the Pharo-dev