Re: [lmi] compelling reason to use 'msysDTK-1.0.1.exe' for setup environment

[Greg Chicares]

On 2005-12-19 15:14 UTC, Boutin, Wendy wrote:
> We once discussed whether or not we really need 'msysDTK-1.0.1.exe'
> and decided we didn't. On Friday, I learned a real good reason to 
> have it: it contains everything we need for cvs and ssh, but I 
> learned the hard way. I couldn't recall how we originally obtained 
> cvs, so I naturally grabbed an archive of the version we use and 
> tried building that from the sources, but it failed in the same 
> way I saw in the office a few weeks ago [I'll share details if 
> you're really interested]. 

That's not pressing. You could take it up on <address@hidden>
if you like; but perhaps it's already been discussed in the archives.

> Anyway, even if I could successfully build cvs from sources, I'd
> still need all the ssh stuff. And since we now have to use ssh to 
> get our sources from savannah, I'd strongly recommend installing 
> 'msysDTK-1.0.1.exe' as part of our setup environment. Do you see 
> any reason why we should refrain from using that in light of my 
> latest re-discovery?

For the msw platform, we need a stable environment with many
customary tools that GNU/Linux provides by default. It appears
that mingw.org meets almost all such needs; to the extent it
does, I favor giving msw users a simple and reliable means of
downloading what they need from that site (our 'setup.make').
Their 'sed' is ancient, and their 'bash' does some msw path
magic that makes it unusable for our purposes, so we need to
replace those; but it's trivial to build 'sed', and there are
other prebuilt shells readily available. Their 'ssh' is old,
but serviceable, and their 'cvs' seems fine, so I agree with
your recommendation to download those as prebuilt binaries.