Hi,
> -Original Message-
> From: wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users-
> boun...@lists.wpkg.org] On Behalf Of Tomasz Chmielewski
> Sent: 10 February 2009 22:06
> To: Chris Wilcox
> Cc: wpkg
> Subject: Re: [wpkg-users] Stopping installations being ca
On 2/10/09, Rainer Meier wrote:
>
> Most of them can be worked around by installing them on a reference
> system (or virtual machine) and just re-package them with 7-zip self
> extractor or similar. Then crate a small batch script whcih is silently
> extracting it, registering some DLL or adding r
Hi Chris,
Chris Wilcox wrote:
> That gets me to my question - the commercial system I use will never
> initiate a package installation if the local and network ini file says
> that the package is already installed. With WPKG, it seems you MUST
> specifiy conditions to prevent this occuring?
This
Chris Wilcox schrieb:
> That gets me to my question - the commercial system I use will never
> initiate a package installation if the local and network ini file says
> that the package is already installed. With WPKG, it seems you MUST
> specifiy conditions to prevent this occuring? Most of t
Hi all,
I'm used to a commercial package allocation tool which behaves a little
differently to WPKG in respect of how it decides if a package is installed or
not. The package install commands are, like WPKG, all held in network based
ini files. Each workstation has a network based and local
