[Glass] Warning: GsDevKitHome scripts for building pharo images are currently broken ...

[Dale Henrichs via Glass]

Lyn,

this isn't a bad idea ... to be honest I have figured that if I were to 
spend the time writing "my own zeroconf script" I would start with the 
current zeroconf script for 30:)

If folks feel that I am too worried about this problem, then just 
editing the script to use the new url is the path I will take ...

If folks would prefer that we "take control of the problem" and manage 
the downloads directly from the web-site, then I will take the time to 
do so while the "iron is hot" I am in the midst of trying to get 1.0.0 
out the door and now would be the time to add the script ...

Dale

On 04/09/2015 09:27 AM, Lyn Headley wrote:
> Maybe you could just set up an http mirror of get.pharo.org 
> <http://get.pharo.org>, and copy the zeroconf script and associated 
> file storage to it. If this is simple, it would last forever and avoid 
> having to learn too much about pharo internals.
>
> On Wed, Apr 8, 2015 at 12:48 PM, Dale Henrichs via Glass 
> <glass at lists.gemtalksystems.com 
> <mailto:glass at lists.gemtalksystems.com>> wrote:
>
>
>     On 04/08/2015 10:02 AM, Johan Brichau wrote:
>
>         It does make sense if you want to keep supporting older versions.
>         So, the question ultimately boils down to wether you want to
>         still build using older versions of Pharo which the Pharo team
>         does no longer ‘support’?
>
>
>     Of the 15 forks of gsDevKitHome, I am the only person running on
>     the latest version of the master branch. So it appears that folks
>     already aren't in the habit of upgrading the scripts and I am
>     worried that in 4 years when I presume Pharo3.0 is dropped from
>     the zeroconf site and you start getting a 404 for the vm30 and
>     pharo30 urls that you guys will be faced with this question ...
>
>     If the Pharo folks said:
>
>       The zeroconf urls will work as long as the site is alive. When a
>       Pharo release goes off support the image, changes, sources and vm
>       download urls will be changed to be static urls that provide the
>     last
>       supported version.
>
>     then this would not be an issue.
>
>     It will definitely be easier to "just use the url", but I don't
>     relish the thought of dealing with the fire drill that I hit
>     yesterday when a perfectly good url starts giving 404's...
>
>     So I am guilty of thinking ahead ... and perhaps I shouldn't worry...
>
>     Dale
>
>
>
>
>     _______________________________________________
>     Glass mailing list
>     Glass at lists.gemtalksystems.com <mailto:Glass at lists.gemtalksystems.com>
>     http://lists.gemtalksystems.com/mailman/listinfo/glass
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20150409/5356df37/attachment.html>