News
2014 news
14-May-2014
WPKG 1.3.1 released. See http://lists.wpkg.org/pipermail/wpkg-announce/2014-May/000077.html for more details.
13-May-2014
WPKG-GP 0.17 released. See http://lists.wpkg.org/pipermail/wpkg-users/2014-May/009840.html for more info.
2011 news
08-Dec-2011
WPKG 1.3 released. See http://lists.wpkg.org/pipermail/wpkg-announce/2011-December/000076.html for more details.
16-Jul-2011
WPKG 1.2 released. See http://lists.wpkg.org/pipermail/wpkg-announce/2011-July/000072.html for more details.
12-Jul-2011
WPKG 1.1.3-RC15 pre-release. See http://lists.wpkg.org/pipermail/wpkg-announce/2011-July/000071.html for more details.
03-Jul-2011
WPKG 1.1.3-RC11 pre-release. See http://lists.wpkg.org/pipermail/wpkg-announce/2011-July/000070.html for more details.
19-Jun-2011
WPKG 1.1.3-RC8 pre-release. See http://lists.wpkg.org/pipermail/wpkg-announce/2011-June/000067.html for more details.
10-Jan-2011
wpkg.org is reachable over IPv6. Please report any connectivity problems you may have.
2010 news
18-Nov-2010
An article about WPKG has been published in the german IT-Magazine "iX" 12/2010 page 132ff.
Gougousoudis, Alexandros: "Softwareverteilung: WPKG und Samba Gruppenrichtlinien für gemischte Umgebungen"
25-Jan-2010
WPKG Client 1.3.10 (testing) has been released.
See the original announcement:
http://lists.wpkg.org/pipermail/wpkg-announce/2010-January/000063.html
2009 news
26-Sep-2009
WPKG 1.1.2 (stable) has been released.
See the original announcement including the full changelog:
http://lists.wpkg.org/pipermail/wpkg-announce/2009-September/000062.html
21-Sep-2009
WPKG Client 1.3.9 has been released.
Small summary (not to be complete):
- 32-bit and 64-bit client versions
- support for /sendStatus switch of wpkg.js 1.1.x (display the progress in the message window)
- support for branding (custom window title and logo)
- remotely start/stop WPKG Service
- using machine credentials for accessing shares
25-Jun-2009
Initial release of a new web frontend of WPKG, wpkgExpress 1.0
See the original announcement:
http://mscdex.blogspot.com/2009/06/ta-da.html
25-Jun-2009
WPKG 1.1.1 (stable) has been released.
See the original announcement including the full changelog::
http://lists.wpkg.org/pipermail/wpkg-announce/2009-June/000061.html
23-May-2009
WPKG 1.1.0 (stable) has been released.
See the original announcement including the full changelog::
http://lists.wpkg.org/pipermail/wpkg-announce/2009-May/000055.html
12-Apr-2009
WPKG 1.1.0-M21 (testing) has been released.
See the original announcement:
http://lists.wpkg.org/pipermail/wpkg-announce/2009-April/000054.html
29-Mar-2009
WPKG 1.0.4 has been released.
See the original announcement:
http://lists.wpkg.org/pipermail/wpkg-announce/2009-March/000051.html
2008 news
03-Nov-2008
WPKG Client 1.3.6 has been released.
- logon delay fixes.
30-Jun-2008
WPKG Client 1.3.4 has been released.
- some minor wpkginst.exe GUI reorganisation,
- 64 bit version.
25-Jun-2008
WPKG Client 1.3.3 has been released.
Only some minor wpkginst.exe GUI reorganisation. Perhaps will be released as 1.4.0-stable soon.
11-Jun-2008
WPKG Client 1.3.2 has been released.
See full release announcement: http://lists.wpkg.org/pipermail/wpkg-announce/2008-June/000048.html.
23-Apr-2008
WPKG 1.0.2 has been released.
See full WPKG-1.0.x changelog.
WPKG 1.1.0-M5 has been released.
See full WPKG-1.1.0-M5 changelog.
16-Apr-2008
WPKG Client 1.2.1 has been released.
Summary: - Fixed bug preventing command-line installation when the settings file was on a password-protected network share.
14-Apr-2008
WPKG 1.0.1 has been released.
See full WPKG-1.0 changelog.
WPKG 1.1.0-M4 has been released.
See full WPKG-1.1.0-M4 changelog.
06-Apr-2008
WPKG 1.0 has been released.
WPKG 1.0-rc9 was released as WPKG-1.0 with no changes.
See full WPKG-1.0 changelog.
WPKG 1.1.0-M3 has been released.
See full WPKG-1.1.0-M3 changelog.
02-Apr-2008
WPKG 1.0-rc9 has been released.
Changes/fixes visible to the user:
Summary:
- Fixed crash when /force was used in conjunction with /synchronize
- Do not force quit if installation fails (unsless /qutonerror is set)
FIX: WPKG crashed when /force was used in conjunction with /synchronize. Fixed.
MOD: WPKG was forced to exit if package checks failed after installation or if
a package failed to remove. This has been changed. Now WPKG prints an
error (unless /quitonerror is used).
Note that installation of packages depending on the failed one will fail
as well. Some packages require reboot unless checks yield true. Therefore
it is crucial to define correct package reboot flags for such packages.
Thanks to Rainer Meier.
10-Mar-2008
WPKG 1.0-rc8 has been released.
Changes/fixes visible to the user:
Summary:
- Fixed missing quote in log output
FIX: Included cosmetic fix for Bug 104 (opening quotation missing).
This fix adds a missing opening quotation in debug output when a new
package is added to the local settings node (after installation success).
FIX: Fixed Bug 103. /help screen is not showing up if config.xml is missing and
null-pointer exception is thrown.
Thanks to Frank Lee and Rainer Meier.
15-Jan-2008
WPKG 1.0-rc7 has been released.
Changes/fixes visible to the user:
Summary:
- Fixed Bug 96 - equality check on non-existing registry key yields exception
FIX: Fixed Bug 96. Equality check on non-existing registry value yields an
exception. The same could theoretically occur as well on IP-address
evaluation. However there it's very unlikely to happen but I fixed it as
well.
Thanks to Rainer Meier.
14-Jan-2008
WPKG 1.0-rc6 has been released.
''Changelog''
Changes/fixes visible to the user:
Summary:
- Added /noremove flag
NEW: Added /noremove flag to skip all package uninstallation actions.
Allows to disable removing of packages. If used in conjunction with the
/synchronize parameter it will just add packages but never remove them.
Instead of removing a list of packages which would have been removed
during that session is printed on exit. Packages are not removed from
the local settings database (wpkg.xml). Therefore it will contain a list
of all packages ever installed.
Note that each package which is requested to be removed (manually or by
a synchronization request) will be checked for its state by executing its
included package checks. If the package has been removed manually it will
also be removed from the settings database. Due to the fact that packages
whithout checks always return 'false' for during the install-status check
these packages will disappear from the local wpkg.xml.
Thanks to Rainer Meier.