Aha, good to know!
> On 9 Jun 2017, at 14:57, Pavel Krivanek <[email protected]> wrote:
>
> We plan to change the sources management. But not immediately.
>
> -- Pavel
>
> 2017-06-09 14:51 GMT+02:00 Yuriy Tymchuk <[email protected]
> <mailto:[email protected]>>:
> Why cannot we have the sources in the image?
>
> When I asked it 2 years ago people were like: "oh, but you can just download
> 1 sources file and use it by all the images". I don’t care about that micro
> space savings, but fine, I said: have it your way. Now as we have to download
> sources all the time, why cannot we just have it IN the image?
>
> Uko
>
>
>> On 9 Jun 2017, at 10:01, Pavel Krivanek <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> Hi,
>>
>> because during the image bootstrapping all source code is reloaded, it is
>> all placed in the changes file and the sources file is useless. It would be
>> strange to deliver Pharo with empty sources file and big changes so we
>> decided to do sources compacting for every build.
>>
>> So Pharo 7 development versions will be delivered in an archive with three
>> files named like:
>>
>> Pharo7.0-117934d.image
>> Pharo7.0-117934d.changes
>> Pharo7.0-117934d.sources
>>
>> where "117934d" is an abbreviated hash of the Git commit from which the
>> Pharo image was bootstrapped. The sources file will be build-specific and of
>> course you will be able to share it between images based on the same build.
>> In changes file you will have only you own changes.
>>
>> You can test it here:
>> https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/lastSuccessfulBuild/artifact/bootstrap-cache/Pharo7.0-117934d.zip
>>
>> <https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/lastSuccessfulBuild/artifact/bootstrap-cache/Pharo7.0-117934d.zip>
>>
>> Cheers,
>> -- Pavel
>>
>
>
