[wpkg-users] [Bug 195] download hangs and wpkg is halted

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=195

Rainer Meier <r.meier at wpkg.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |r.meier at wpkg.org
         Resolution|                            |WONTFIX

--- Comment #2 from Rainer Meier <r.meier at wpkg.org>  ---
Honestly speaking I always hated the download feature. It's still there due to
legacy compatibility as this feature was introduced before I've joined the
project. Download capabilities of XMLHTTP object in WSH are pretty poor. There
were a couple of requests already regarding MD5/SH1 checksumming and further
advanced download features. Unfortunately it is not possible with WSH to
implement such features in any acceptable way.
The only option would likely be to use external applications like wget.exe for
download and other tools for checksumming.

There was a longish discussion on the mailing list recently:
<http://lists.wpkg.org/pipermail/wpkg-users/2011-July/007656.html>

The result was that it would potentially be possible to ship a wrapper script
which takes a few parameters like download URL, download source and a checksum.
So this external script could take care about the download process.

In fact such a script would not have to be invoked via the <download /> tag but
instead as a simple command like <install />. So it allows much more
flexibility in passing checksums, URLs and target folders.

So what I recommend is to use the WPKG <download /> feature only for very, very
basic file downloads and for everything else just add a command which calls an
external downloader tool. This allows much more flexibility and also error
handling via WPKG exit code evaluation.

-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.