[wpkg-users] Testing updates

[Malte Starostik]

Hi Lukasz,

one way to do this is to keep a testing copy of all WPKG files and setups and 
make your test clients use this instead of the production files.  This way you 
get a completely separate base dir and %SOFTWARE%.  You can test different 
packages, profiles, to some extent hosts, different versions of WPKG as well 
as changes to the software repository.  When all is well, you can rsync the 
testing tree to the production one and get the new setup for all clients.  
Saves you from possible problems with changing package ids.
I'm using samba with the expand_msdfs VFS module to relay clients to the 
testing or production trees based on their IP address.  This way, they can all 
use the same UNC paths and the server decides which version they get.  This 
eliminates problems with MSI getting angry when the installation path is 
changed behind its back and there is no need to modify any paths after syncing 
back to production.

HTH,
Malte

Am Mittwoch, 21. Oktober 2009 20:12:01 schrieb Lukasz Zalewski:
> Hi all,
> What is the best way to thes updates to the already deployed packages?
> We have quite few packages at the top level of profiles hierarchy
> (covering nearly all of the machines).
> Remving package from there and putting it in the test profile would be
> disasterous. What i have been doing so far is: make a copy of a package,
>   change package id, apply, upgrade the revision and appropriate
> install/upgrade/remove tags, apply - if all is well copy the package to
> its original file and package id. Is there a more efficient way to do this?
> 
> May thanks
> 
> Luk
> -------------------------------------------------------------------------
> wpkg-users mailing list archives >>
>  http://lists.wpkg.org/pipermail/wpkg-users/
>  _______________________________________________
> wpkg-users mailing list
> wpkg-users at lists.wpkg.org
> http://lists.wpkg.org/mailman/listinfo/wpkg-users
>