Re: [Mingw-users] PuTTY as local MSYS terminal? (ConEmu)

[Keith M. <kei...@us...>]

On 09/09/12 10:12, Maximus wrote:
> Keith Marshall <keithmarshall@...> writes:
>> Understood.  So, you split it into the two packages, as below.  Users on
>> x86 install only the mingw32 package.  Users on x86_64 request the
>> installation of only the mingw64 package, which you have declared as
>> requiring the mingw32 package, (within the mingw-get XML package
>> specification), and mingw-get installs both packages.
>
> I'm not familiar with mingw structure, and have one doubdt about this split.
> For example, user had installed x86 version of mingw.
> There is no restrictions for running it on 64-bit OS, isn't it?

Perhaps I'm being unnecessarily paranoid, but I'm mindful of a likely 
plethora of bug reports, from x86 users, along the lines of: "Hey, why 
have you idiots installed these useless 64-bit binaries on my 32-bit host?"

> I mean, x86 version of ConEmu starts x86 version of bash (OK),
> but user runs them on 64-bit OS and type in prompt "telnet",
> but this tool is available only in 64-bit version. And ConEmu
> will fails, if x86_64 version of ConEmu is not installed too.
>
> (example may be far-fetched, illustration only).
>
> ConEmu check existence of required libraries on startup,
> and if ConEmuHk64.dll is not found in 64-bit OS - warning
> will be shown, but allowing to continue.
>
>      Recommended files not found!
>      ConEmuHk64.dll

So, the 64-bit user who installs only the 32-bit package, will get a 
warning of a potential problem, and can take action (install the 64-bit 
package) to avoid it.

> If you think, this case is not a problem - packages may be splitted easily.

I don't think it's a problem, but if your concern remains, perhaps you 
could install an integrated package, and devise a post-install hook to 
to remove the 64-bit components from 32-bit hosts?

-- 
Regards,
Keith.