If you’re using Wpkg and are interested in a chat, or any of my package files, then do feel free to get in touch on Linked In or by email.

Things have grown from those early days, and there are now 91 “packages” under management, including approximately 57 different applications, 3 sets of application configuration, and 20 plugins.

Here are a few tips / patterns that I have adopted to make life easier along the way.

To get started you can just download the WPKG server package and unzip it to a network drive (on your home server, right).

This sets up a folder structure into which you can add your software installers and the XML data.

Each of my packages now has a header section providing key information for upgrades and a version history, e.g.: It’s one of those fun weekly chores – going through all the software installed on your Windows PC and checking online for updates, downloading them to a USB stick (the bigger ones at least), and then going round each PC in turn to install them.

We’ve got 4 PCs to update, and that can’t be uncommon in a modern household.

In this case it's up to the user then to check if vcredist must be manually installed, too. x86 was compiled with VS2008 to support XP for as long as possible, x64 was compiled with VS2013.

I have created new installers for the recent backport fix 0.16.6704 https://github.com/Free CAD/Free CAD/releases/tag/0.16 https://sourceforge.net/projects/free-c ...

You may have read my previous post about managing Windows updates with WPKG.

I’ve been using this system for over a year now, and it has saved me a huge amount of time and provided peace of mind that the applications on my various Windows machines are properly up-to-date.

The other advantange of this way of doing things is that it uses a user-space network connection to the fileshare where your Wpkg source files are held, thus avoiding some hiccups in Wpkg where the System user can’t establish the network connection required to update in the background.