> On 21 Jun 2018, at 10:20, Guido Chari <cha...@gmail.com> wrote:
> 
> Seriously? Are you talking about the README of this repo 
> https://github.com/pharo-project/pharo-minimal-scripts? 
> <https://github.com/pharo-project/pharo-minimal-scripts?>
yes, seriously.
I’m talking about the readme of pharo:
Bootstrapping Pharo from sources

To bootstrap a new Pharo image you need the latest stable version of Pharo. For 
more information about bootstrapping, refer to guillep/PharoBootstrap 
<https://github.com/guillep/PharoBootstrap>.

The bootstrapping can be done using the following script:

BUILD_NUMBER=42 BOOTSTRAP_ARCH=32 sh ./bootstrap/scripts/bootstrap.sh


> 
> El jue., 21 jun. 2018 a las 10:02, Esteban Lorenzano (<esteba...@gmail.com 
> <mailto:esteba...@gmail.com>>) escribió:
> 
> 
>> On 21 Jun 2018, at 09:18, Guido Chari <cha...@gmail.com 
>> <mailto:cha...@gmail.com>> wrote:
>> 
>> 
>> 
>> El lun., 11 jun. 2018 a las 21:25, Hernán Morales Durand 
>> (<hernan.mora...@gmail.com <mailto:hernan.mora...@gmail.com>>) escribió:
>> Hi Pablo,
>> 
>> 2018-06-11 6:06 GMT-03:00 teso...@gmail.com <mailto:teso...@gmail.com> 
>> <teso...@gmail.com <mailto:teso...@gmail.com>>:
>> > You can execute the bootstrap process.
>> 
>> How you do that?
>> 
>> Yes,  I am wondering the same.
> 
> guys, is written in the README (I don’t want to be rude, but that would be 
> RTFM ;) )
> now *after* that, there can be problems. We will be pleased to hear about 
> them and help :)
> 
> cheers!
> Esteban
> 
> 
>> Is it any documentation on how to run the bootstrap process? In my case I 
>> need an image that is functional, but as small as possible. 
>>  
>> 
>> > However, maybe that is not required, as the bootstrapped images for Pharo7
>> > are stored.
>> >
>> >
>> > These are the latest (always):
>> >
>> > Compiler:
>> > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/lastSuccessfulBuild/artifact/bootstrap-cache/Pharo-compiler-7.0.0-alpha.build.1037.sha.7fc6bdf.arch.32bit.zip
>> >  
>> > <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/lastSuccessfulBuild/artifact/bootstrap-cache/Pharo-compiler-7.0.0-alpha.build.1037.sha.7fc6bdf.arch.32bit.zip>
>> > Compiler + Traits:
>> > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/lastSuccessfulBuild/artifact/bootstrap-cache/Pharo-core-7.0.0-alpha.build.1037.sha.7fc6bdf.arch.32bit.zip
>> >  
>> > <https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/lastSuccessfulBuild/artifact/bootstrap-cache/Pharo-core-7.0.0-alpha.build.1037.sha.7fc6bdf.arch.32bit.zip>
>> >
>> 
>> Both links return a:
>> 
>> Problem accessing
>> /pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/lastSuccessfulBuild/artifact/bootstrap-cache/Pharo-core-7.0.0-alpha.build.1037.sha.7fc6bdf.arch.32bit.zip.
>> Reason:
>> 
>>     Not Found
>> 
>> Btw, aren't the miniaml images in http://files.pharo.org/image/60/ 
>> <http://files.pharo.org/image/60/> usable? Is there any 64bit compatible 
>> minimal image available?
>>  
>> 
>> Cheers,
>> 
>> Hernan
>> 
>> > These are the first images that are usable, the first one has a compiler 
>> > and
>> > the second adds the traits implementation.
>> > As Esteban said, you can modify the process to bootstrap whatever you want.
>> > However, having an image that does not have compiler it is more difficult 
>> > to
>> > use.
>> >
>> > If you define better what do you call a minimal image we can help you more.
>> >
>> > Cheers,
>> > Pablo
>> >
>> >
>> > On Mon, Jun 11, 2018 at 10:30 AM, Guido Chari <cha...@gmail.com 
>> > <mailto:cha...@gmail.com>> wrote:
>> >>
>> >> Hi,
>> >>
>> >> Is there any way to build a minimal (kernel) pharo image or at least some
>> >> kind of small image without the whole default packages?
>> >>
>> >> Best regards,
>> >> Guido.
>> >
>> >
>> >
>> >
>> > --
>> > Pablo Tesone.
>> > teso...@gmail.com <mailto:teso...@gmail.com>
>> 
> 

Reply via email to