On 23 Mar 2015, at 17:43, Marcus Denker <marcus.denker@inria.fr> wrote:
On 23 Mar 2015, at 17:38, Dale Henrichs <dale.henrichs@gemtalksystems.com <mailto:dale.henrichs@gemtalksystems.com>> wrote:
I don't need zeroconf for my Pharo1.1 app, either. Alternate download methods would be fine.
I continue to support Metacello on all of the older versions of Pharo and I do use zeroconf there, but if there is an alternate download mechanism then I can use that for testing â¦
Download will be available eternally:
http://files.pharo.org/image/ <http://files.pharo.org/image/> http://files.pharo.org/vm/ <http://files.pharo.org/vm/>
The thing is that get.pharo.org <http://get.pharo.org/> is more than a download. People will expect that it *works*. And we can not (we really can not) support all versions of Pharo. E.g. Spur. Soon we will have a VM that can not run old images. If we keep get.pharo.org <http://get.pharo.org/> for 1.4, people expect it to work. And we will have to provide a VM for the old version. Then at some point, this VM will not work anymore on the then current linux. Then people expect us to fix that. Just downloads is a different thing: this is an archive, use it at your own risk. Marcus