Re: [Bug-wget] wget on Windows 64-bit

[Micah Cowan]

On 06/20/2012 11:19 AM, John wrote:
> 
> 
> "Jochen Roderburg" <address@hidden> wrote in message
> news:<address@hidden>...
>> Zitat von Jochen Roderburg <address@hidden>:
>>
>> > Search an archive for this mailing list.   ;-)
>> > Windows test builds from recent development snapshots were
>> announced  a > few times here.
>>
>> Found them again via another way.  ;-)
>>
>> http://sourceforge.net/projects/getgnuwin32/files/getgnuwin32/test%20builds/
>>
>>
>> Regards, Jochen Roderburg
>>
> 
> Jochen, hello.
> 
> I really appreciate your having provided this link. I cannot imagine
> there being a more recent version available.  There are a lot of files
> included in this large 15.8 Mb archive:
> 
> wget-1.13.4.56-620c__mingw__05-23-12.zip
> 
> There are other archives shown on this page, but I assume that this is
> the one I am looking for.  Do I understand correctly that all of these
> files are needed to run wget?  Apparently, I was mistaken about the
> number of files needed for it to run, as I was not expecting there to be
> so many. Thanks.

Not all those files are required to run wget. It looks like it's the
full binary install for several packages that may be used to build wget,
and perhaps a couple of items that aren't used for that at all (curl.exe
is an obvious example).

Picking what's needed from what's not needed could be difficult to do
safely, though, so you might consider leaving everything there. From a
first glance, though, I'd expect you could safely remove everything in
root/share/doc, root/share/emacs, root/share/gettext, and root/share/man
(there's a wget.1 in there, but then perhaps you don't have a "man"
command installed, and you can always get the more-complete
documentation from the website).

I imagine any .exe files other than wget can be removed. I'd leave all
the dlls to be safe, though.

-mjc