Hi,

On Tue, Jun 18, 2013 at 11:00 AM, Matej Horvat
<[email protected]> wrote:
>
>> 2). Regarding Wget, actually I don't use a lot of such tools (though
>> I've used it sparingly before), but couldn't you just automatically
>> grab (via Windows' existing FTP.EXE or maybe something better I'm not
>> aware of) the Win32 WGET.EXE if not found in %PATH%?
>
> I didn't consider that. But I'd rather not hardcode any URLs into the EXE,
> and I don't think it's too hard to install it manually. Is there even an
> official FTP site with Windows executables of Wget?

Dunno, lemme check. Sometimes GNU does indeed host Windows binaries.
Hmmm, I don't see anything on this particular mirror I'm checking. My
Cygwin install does have it, but I don't think it's installed by
default (doubt it's in their "base").

You could always use cURL instead. It does seem to have links to
various Win32 builds:

http://curl.haxx.se/

>> 3). "Edit GETPKGS.CFG so that the "WGET=" line contains the path and
>> filename
>>   of your Wget executable."
>>
>> Again, wouldn't just checking the %PATH% for it be easier?
>
> Maybe. On my system, PATH is very long already, mostly due to various
> compilers and poorly written programs that insist on being in the PATH.

I agree, %PATH% is misused. But it still shouldn't be that hard to
check for wget.exe there. In fact,
starting with Vista (NT 6+) on up, you can use "where.exe /q wget" to
silently check for it (as it returns
an appropriate errorlevel: zero if found, one if not).

> Putting the path into the configuration file just seemed a better solution
> to me.

Okay, but it's more tedious.

>> 4). "The DOSDIR environment variable must be set and it must not end
>> with a
>>   backslash. Usually, it will already be set."
>>
>> I hope your error checking is good.   :-)
>
> I check that DOSDIR exists and that it doesn't end with a backslash, but I
> trust the user to point it to a valid location.

It can't be that hard to check if the directory exists.

> I assume that most users
> only set DOSDIR once (or never, if the FreeDOS installer does it for them)
> and then forget about it.

It's probably not a major problem, but still ... making things easier
and more robust isn't always a bad thing.

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to