Dimitris, As Guile explained it, it is a matter of responsibility to include a package in the Pharo image. The more packages in the base Pharo image the more complicated is the release process for the Pharo team, and more stress, etc. Nevertheless, a complement Pharo release with additional packages is possible and can be automated with Jenkins. But another team need to take this specific responsibility. The Smalltalk community has been discussing this matter for decades. Hope it clarify Hilaire Le 28/10/2016 à 15:05, Guille Polito a écrit :
What I mean, adding a package inside the image can bring also a lot of problems to package maintainers, so doing it just because "others do it" is not a good argument.
-- Dr. Geo http://drgeo.eu