Marcus,
This makes perfect sense to me ... If zeroconf is only used for the
supported versions of Pharo that is perfectly fair ...
When a version goes off of zeroconf support it would be convenient if
one could find the appropriate "eternal download urls" for the image/vm
otherwise how would I know?
Keep in mind, that I use zeroconf to download for travis-based tests and
I don't have a physical disk to look at ... and it is possible that I
won't know that a particular version has gone off of zeroncof support
until my build fails ... so it would be _convenient_ to be able to
lookup the image/vm combo that I need to use...
Dale
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
