Johannes.Brix | 2 Jan 16:54 2009

remove does not work of type <check type="file" condition="versionequalto" path="%programfiles%\pidgin\pidgin.exe" value="2.5.3.0" />

Hello,

I don't know if this is a bug of wpkg.js or of my config, 
but removing this package doesn't remove it from wpkg.xml.

<package
   id="pidgin"
   name="Pidgin"
   revision="2530"
   reboot="false"
   priority="1">
   <check type="file" condition="versionequalto" 
path="%programfiles%\pidgin\pidgin.exe" value="2.5.3.0" />
   <install cmd='cmd /C taskkill /F /T /IM pidgin.exe' >
      <exit code='1' />
      <exit code='128' /> 
   </install> 
   <install cmd='\\evd-ads2\wpkg\Pidgin\pidgin-2.5.3.exe /L=1031 /S /NOUI' 
/>
   <install cmd='\\evd-ads2\wpkg\Pidgin\pidgin-install.cmd' />
   <upgrade cmd='cmd /C taskkill /F /T /IM pidgin.exe' >
      <exit code='1' />
      <exit code='128' /> 
   </upgrade> 
   <upgrade cmd='\\evd-ads2\wpkg\Pidgin\pidgin-2.5.3.exe /L=1031 /S /NOUI' 
/>
   <upgrade cmd='\\evd-ads2\wpkg\Pidgin\pidgin-install.cmd' />
   <remove cmd='\\evd-ads2\wpkg\Pidgin\pidgin-remove.cmd' >
      <exit code='0' />
   </remove>
(Continue reading)

Johannes.Brix | 2 Jan 17:21 2009

remove does not work of type <check type="file" condition="versionequalto" path="%programfiles%\pidgin\pidgin.exe" value="2.5.3.0" />

Hello,

I don't know if this is a bug of wpkg.js or of my config, 
but removing this package doesn't remove it from wpkg.xml.

<package
   id="pidgin"
   name="Pidgin"
   revision="2530"
   reboot="false"
   priority="1">
   <check type="file" condition="versionequalto" 
path="%programfiles%\pidgin\pidgin.exe" value="2.5.3.0" />
   <install cmd='cmd /C taskkill /F /T /IM pidgin.exe' >
      <exit code='1' />
      <exit code='128' /> 
   </install> 
   <install cmd='\\evd-ads2\wpkg\Pidgin\pidgin-2.5.3.exe /L=1031 /S /NOUI' 
/>
   <install cmd='\\evd-ads2\wpkg\Pidgin\pidgin-install.cmd' />
   <upgrade cmd='cmd /C taskkill /F /T /IM pidgin.exe' >
      <exit code='1' />
      <exit code='128' /> 
   </upgrade> 
   <upgrade cmd='\\evd-ads2\wpkg\Pidgin\pidgin-2.5.3.exe /L=1031 /S /NOUI' 
/>
   <upgrade cmd='\\evd-ads2\wpkg\Pidgin\pidgin-install.cmd' />
   <remove cmd='\\evd-ads2\wpkg\Pidgin\pidgin-remove.cmd' >
      <exit code='0' />
   </remove>
(Continue reading)

Rainer Meier | 4 Jan 12:30 2009

Re: remove does not work of type <check type="file" condition="versionequalto" path="%programfiles%\pidgin\pidgin.exe" value="2.5.3.0" />

Hi Johannes,

Johannes.Brix <at> evidian.com wrote:
> I don't know if this is a bug of wpkg.js or of my config, 
> but removing this package doesn't remove it from wpkg.xml.

Let's check.

> <package
>    id="pidgin"
>    name="Pidgin"
>    revision="2530"
>    reboot="false"
>    priority="1">
>    <check type="file" condition="versionequalto" 
> path="%programfiles%\pidgin\pidgin.exe" value="2.5.3.0" />
>    <install cmd='cmd /C taskkill /F /T /IM pidgin.exe' >
>       <exit code='1' />
>       <exit code='128' /> 
>    </install> 
>    <install cmd='\\evd-ads2\wpkg\Pidgin\pidgin-2.5.3.exe /L=1031 /S /NOUI' 
> />
>    <install cmd='\\evd-ads2\wpkg\Pidgin\pidgin-install.cmd' />
>    <upgrade cmd='cmd /C taskkill /F /T /IM pidgin.exe' >
>       <exit code='1' />
>       <exit code='128' /> 
>    </upgrade> 
>    <upgrade cmd='\\evd-ads2\wpkg\Pidgin\pidgin-2.5.3.exe /L=1031 /S /NOUI' 
> />
>    <upgrade cmd='\\evd-ads2\wpkg\Pidgin\pidgin-install.cmd' />
(Continue reading)

Johannes.Brix | 5 Jan 10:50 2009

remove does not work of type <check type="file" condition="versionequalto" path="%programfiles%\pidgin\pidgin.exe" value="2.5.3.0" />

Hello Rainer,

your analysis is so far correct, but the conclusion is not.
Here is my uninstall script.
-----
 <at> echo off
:: Remove Pidgin 
::
:: By: Johannes Brix, Evidian, 2009/01/02
:: ==================================================
:: Modifications
:: ==================================================

SET logdir=\\Evd-ads2\wpkg\0base\config\%COMPUTERNAME%
SET logcmd=\\Evd-ads2\wpkg\0base\trace.cmd

call %logcmd% Pidgin-Remove Pidgin-Remove started -----------------------

:killproc
taskkill /F /T /IM pidgin.exe
tasklist | findstr pidgin.exe
IF "%ERRORLEVEL%"=="0" goto killproc

RD /S /Q "%ProgramFiles%\Pidgin\pixmaps\pidgin\emotes\kolobok_big_pack"
call %logcmd% Pidgin-Remove Pidgin-Remove AddOns ended 
-----------------------

%ProgramFiles%\Pidgin\pidgin-uninst.exe /S

call %logcmd% Pidgin-Remove Pidgin-Remove ended -----------------------
(Continue reading)

Tomasz Chmielewski | 5 Jan 10:59 2009

Re: WPKG Client 1.3.6 64bit error

Adam Williams schrieb:
> Tomasz Chmielewski wrote:
>> Could you try if this one installs for you?
>>
>> http://www1.wpkg.org/files/client/beta/test/
>>
> 
> i still get the same error message.

Anyone else out there using WPKG Client on Vista 64 bit?

--

-- 
Tomasz Chmielewski
http://wpkg.org
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
Kamil Maciejewski | 5 Jan 12:02 2009
Picon

Install/Upgrade a package only if this program is installed


--

.style1 {font-size: 8px; font-family: Verdana, Arial, Helvetica, sans-serif; font-weight: bold;} .style2 { font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 12; color: #000000; } 

 Hello. I have a question - since there is a group of programs that users can install even without admin rights and there are some programs that we need to install only on some machines without changing WPKG group membership I'd like to ask - is there a possibility to create a package in the main default group that would install the latest version of the program only if there's an older version.

Example:

If there is Winamp installed -> install the latest version (tags <install> or <upgrade>
if no Winamp installed -> do nothing and exit with '0' code.

I know I can go around and do this with doing something like this:

<check type="logical" condition="or">
<check type="uninstall" condition="exists" path="Winamp" />
<check type="file" condition="exists" path="c:\SOME_FILE.TXT" />
<install cmd="IF EXIST C:\PROGRAM FILES\WINAMP\WINAMP.EXE THEN %SOFTWARE%\WINAMP\SETUP.EXE /S /install=SFQR" ELSE COPY %SOFTWARE%\SOME_FILE.TXT C:" />

So it will always execute the package and install Winamp if there's an older version or copy the SOME_FILE.TXT file if there's no winamp at all, and then if winamp is installed or the file is present it will check the package installation is OK.

But I would rather like to create a package that would not be run at all if there would be no winamp istalled. Is this possible?


-------------------------------------------------------------------------
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
Josh Frome | 5 Jan 12:20 2009

WPKG and Windows SteadyState Disk Protection

Hello,

     I'm new to WPKG and was wondering if anyone had tips for integrating Microsoft's SteadyState disk
protection.  More specifically, SteadyState is configured to remove any changes the the hard drive (a la
Deep Freeze, etc) and requires a registry change and reboot to write/save changes to the hard drive.  I have
a script that will perform the registry modification and reboot, but I am looking for a way to only call the
script when WPKG has made a change (install/uninstall, etc) and not every time WPKG runs (i.e. using a post-action).

What would be the best approach to find out if WPKG has installed/uninstalled packages and if so, enable a
reboot script?

Thanks,

Josh

--

-- 
Josh Frome
Network Administrator
Salt Lake City Public Library
801.524.8282
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
mscdex | 5 Jan 14:37 2009
Picon

Re: WPKG and Windows SteadyState Disk Protection

I ran into a similar situation when I was working with a small network that was using deep freeze. I ended up modifying wpkg.js in the relevant places where a successful package installation/removal/upgrade/downgrade has been detected, etc. In those places, I had it call a custom jscript function of mine to do the freezing (and reboot possibly, I can't remember now) of the hard disk after all was said and done. I also put in a call to a custom jscript function to do a thaw (and reboot) first only if wpkg detected that work needed to be done (packages needed to be removed, installed, etc).

That may not be the most elegant solution, but I couldn't find any neater way to do it.

On 1/5/09, Josh Frome <jfrome <at> maildev.slcpl.org> wrote:
Hello,

     I'm new to WPKG and was wondering if anyone had tips for integrating Microsoft's SteadyState disk protection.  More specifically, SteadyState is configured to remove any changes the the hard drive (a la Deep Freeze, etc) and requires a registry change and reboot to write/save changes to the hard drive.  I have a script that will perform the registry modification and reboot, but I am looking for a way to only call the script when WPKG has made a change (install/uninstall, etc) and not every time WPKG runs (i.e. using a post-action).

What would be the best approach to find out if WPKG has installed/uninstalled packages and if so, enable a reboot script?

Thanks,

Josh

--
Josh Frome
Network Administrator
Salt Lake City Public Library
801.524.8282
-------------------------------------------------------------------------
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

-------------------------------------------------------------------------
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
Rainer Meier | 6 Jan 01:09 2009

Re: remove does not work of type <check type="file" condition="versionequalto" path="%programfiles%\pidgin\pidgin.exe" value="2.5.3.0" />

Hi Johannes,

OK, this gives a good impression of what you do exactly. I will try to
re-produce the problem.

You're right if you assume that I prefer the uninstall entry check ;-)

br,
Rainer

Johannes.Brix <at> evidian.com wrote:
> Hello Rainer,
> 
> your analysis is so far correct, but the conclusion is not.
> Here is my uninstall script.
> -----
>  <at> echo off
> :: Remove Pidgin 
> ::
> :: By: Johannes Brix, Evidian, 2009/01/02
> :: ==================================================
> :: Modifications
> :: ==================================================
> 
> SET logdir=\\Evd-ads2\wpkg\0base\config\%COMPUTERNAME%
> SET logcmd=\\Evd-ads2\wpkg\0base\trace.cmd
> 
> call %logcmd% Pidgin-Remove Pidgin-Remove started -----------------------
> 
> :killproc
> taskkill /F /T /IM pidgin.exe
> tasklist | findstr pidgin.exe
> IF "%ERRORLEVEL%"=="0" goto killproc
> 
> RD /S /Q "%ProgramFiles%\Pidgin\pixmaps\pidgin\emotes\kolobok_big_pack"
> call %logcmd% Pidgin-Remove Pidgin-Remove AddOns ended 
> -----------------------
> 
> %ProgramFiles%\Pidgin\pidgin-uninst.exe /S
> 
> call %logcmd% Pidgin-Remove Pidgin-Remove ended -----------------------
> exit /B 0
> -----
> 
> The return value is 0 and this is OK for wpkg.
> The folder of Pidgin is totally removed, nothing left when wpkg takes 
> control again.
> 
> I just did a test with the check method:
>    <check type="uninstall" condition="exists" path="Pidgin" />
> 
> Here the deinstallation works fine.
> I think there is a bug somewhere in wpkg with the check against file 
> version methode like
> <check type="file" condition="versionequalto" 
> path="%programfiles%\pidgin\pidgin.exe" value="2.5.3.0" />.
> It seems that the variable is not refreshed after the deinstallation.
> 
> Some months ago I had the same similar problem with jxplorer, where also 
> the file check methode was configured
> and it was impossible to remove it from wpkg.xml local config file.
> 
> Kind regards,
> Johannes
> -------------------------------------------------------------------------
> 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
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/
Rainer Meier | 6 Jan 01:14 2009

Re: Install/Upgrade a package only if this program is installed

Hi,

Currently there is no such feature because it would mean to follow a
completely different approach. You would need checks to check if a
program is installed and additional checks which verify the installed
version. These checks are not necessarily identical.

In a future version of WPKG I plan a feature which allows the user to
install packages using WPKG and manually added packages are treated the
same way as if they were added by the profile allowing automatic
upgrading even if the package is not part of the profile. Of course this
would require the user to have rights to install the package (but not
necessarily admin rights if the package can be installed properly
without admin rights).

However this still implies that the package has been installed using
WPKG (and not manually).

br,
Rainer

Kamil Maciejewski wrote:
> 
> -- 
> 
> ------------------------------------------------------------------------
> 
>  Hello. I have a question - since there is a group of programs that
> users can install even without admin rights and there are some programs
> that we need to install only on some machines without changing WPKG
> group membership I'd like to ask - is there a possibility to create a
> package in the main default group that would install the latest version
> of the program only if there's an older version.
> 
> Example:
> 
> If there is Winamp installed -> install the latest version (tags
> <install> or <upgrade>
> if no Winamp installed -> do nothing and exit with '0' code.
> 
> I know I can go around and do this with doing something like this:
> 
> <check type="logical" condition="or">
> <check type="uninstall" condition="exists" path="Winamp" />
> <check type="file" condition="exists" path="c:\SOME_FILE.TXT" />
> <install cmd="IF EXIST C:\PROGRAM FILES\WINAMP\WINAMP.EXE THEN
> %SOFTWARE%\WINAMP\SETUP.EXE /S /install=SFQR" ELSE COPY
> %SOFTWARE%\SOME_FILE.TXT C:" />
> 
> So it will always execute the package and install Winamp if there's an
> older version or copy the SOME_FILE.TXT file if there's no winamp at
> all, and then if winamp is installed or the file is present it will
> check the package installation is OK.
> 
> But I would rather like to create a package that would not be run at all
> if there would be no winamp istalled. Is this possible?
> 
> ------------------------------------------------------------------------
> **
> 
> *
> *
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> 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
-------------------------------------------------------------------------
wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/

Gmane