Re: [Mingw-users] Automated MinGW installer outdated?

[Earnie B. <ea...@us...>]

Quoting Brian Dessent <br...@de...>:

> Earnie Boyd wrote:
>
>> That should be doable.  Are you willing to craft the commands?  I'll
>> get them in the .htaccess file.
>
> Try the following as a starting point:
>
> RewriteEngine On
> RewriteRule ^/mingw\.ini$ 
> http://mingw.cvs.sourceforge.net/viewvc/*checkout*/mingw/MinGW/inifiles/mingw.ini?pathrev=MinGW-5_1 
> [R]
>

Because of other rewrite rules for Drupal Clean URL it doesn't function 
well.  Besides, I don't think the web server will allow connecting to 
the cvs server (see below).

> There are two potential problems with this approach:
>
> 1. The installer might not have the intelligence to follow a HTTP 30x
> redirect.  With mod_rewrite you can avoid this with an internal redirect
> but only when both resources are on the same server, which is not the
> case with www.mingw.org vs. mingw.cvs.sourceforge.net.
>

The change may need to happen in the installer.  I wrote a script using 
a passthru command of wget -O- -q and while ``php mingw.ini'' returned 
the data I just get a timeout when executing the php from the browser.

> 2. There is a possibility that SF would not appreciate the increased
> load of every installer run hitting the dynamic ViewVC script -- I seem
> to recall their CVS servers are often overloaded.  In that case I think
> it would make more sense to install a cronjob that runs daily or hourly
> (or a checkin-hook) which updates the static copy at mingw.org/mingw.ini
> from the one in CVS.  That would achieve the same goal of not requiring
> manual care to update the file every time it changes but without the
> extra load of serving it dynamically for every hit.
>

Now that we have a virtual shell service I think I can push it from 
another server.  At least until SF gives us a cron process.

Earnie