Re: [Mingw-users] MinGW 5.1.2 installer evaluation

[Dave M. <win...@nt...>]

Earnie Boyd wrote:
> Quoting John Vandenberg <ja...@gm...>:
>
>   
>> After installing Candidate, I wanted to download and install Current
>> beside Candidate; the installer only wanted to check Candidate for
>> updates.  I uninstalled Candidate, and the installer then let me
>> download Current.  Is there any way I can use the installer to track
>> both?
>>
>>     
>
> I just asked that Q to the developer and still waiting response.  I 
> will be changing it soon for the MSYS release candidate.
>
>   
Was that mail to me? If so, it vanished into the ether somewhere 
unfortunately.

This sort of feature needs a bit of thinking about.

I suppose we could allow the user to choose a package to install or 
update at every startup rather than just on initial install. We would 
need to store paths for each package and check the user is not 
attempting to install different packages in the same directory.

Would it be reasonable to require an installer run to update each of the 
packages a user has installed? I think the code might get a little out 
of hand if we attempted to update all packages with a single run.
>> When it is downloading the packages, it is regularily hanging at the
>> message "Connecting ...".  After a few minutes it will tell me that my
>> Internet connection is down (it definitely isn't) , and I can retry.
>> Usually after a few retries, the process will continue.  Is there a
>> debug build I can use to provide a more detailed picture of what is
>> going wrong?  or instructions on how I can build the installer from
>> source?
>>
>>     

This sounds like it's related to the SF script that picks a mirror 
giving you a server that you're having problems with. I'm not sure if we 
can do anything about that unfortunately.

I've now uploaded 5.1.3.

The problems with previous and candidate installing packages from 
current have been fixed - a minor issue with the fallback to current if 
an individual component does not exist for the package being installed.

I've also attempted to compensate for the + in filename problem by 
replacing this character with %2b when downloading. This works for me, 
unfortunately the two people I'd found who had this problem no longer 
have it :/ Perhaps SF have fixed it on their end now.

Dave