Hi Marco,
On 18.07.2011 15:24, Marco Gaiarin wrote:
Mandi! Rainer Meier
In chel di` si favelave...
So for me there would be only one compromise we could potentially think about:
Ship WPKG with a download-helper script.
I ''vote'' for this compromise. ;-)
Really: someone insert the<download /> tag, so seems to me a bad idea
to remove it. So:
a) extend a little with a md5="" and/or sha="" tag, totally ignored by
the internal WSH downloader
b) extend a little wpkg.js to support an external downloader, as an
option (so, default use the internal)
c) build an (example) external download script; i can do some try on
the last, but really i've little cmd.exe knowledge...
I've just committed a downloader script which allows advanced downloading via
existing commands. Maybe it resolves the issue.
I do not plan yet to include functionality in WPKG to call downloader from
within <download /> tags as this would clutter package definition with
attributes which are not used by WPKG and it would increase complexity in case
more checksums (SHA2...) are added. From my point of view calling downloader
directly from commands is the most simple and flexible solution.
Some discussion can be followed here:
<http://bugzilla.wpkg.org/show_bug.cgi?id=195>
br,
Rainer
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
_______________________________________________
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
