[wpkg-users] Acrobat Pro Security Updates - Check if last full update was installed?

[Stefan Pendl]

Am 26.08.2014 10:23, schrieb Nils Thiele:
> Hey,
> I was wondering what is the best way to integrate small security 
> updates (Acrobat Pro for example).
> The Problem is that those small updates wont include the last ones and 
> so it wont work if the latest version isnt installed. Because of this 
> i cant remove the latest full update from my wpkg package.
> The downside is that with this it reinstall the full package before 
> the small update even tho it is already installed and it takes a lot 
> more time.
>
> I cant just remove the fullupdate because we have lots of clients that 
> arent regulary turned on so if those start up again they depend on the 
> latest full update for sure.
> The small security fix also increases the version number.
>
> My current update method looks like this:
>
> <!-- Full Update -->
> <upgrade cmd='msiexec /qn /norestart /update 
> "%SOFTWARE%\Adobe\Acrobat\AcrobatUpd10110.msp"' >
>                 <exit code="0" />
>                 <exit code="3010" reboot="postponed" />
> </upgrade>
> <!-- Small Security Fix -->
> <upgrade cmd='msiexec /qn /norestart /update 
> "%SOFTWARE%\Adobe\Acroba\AcrobatSecUpd10111.msp"'>
>                 <exit code="0" />
>                 <exit code="3010" reboot="postponed" />
> </upgrade>
>
> Is there a way to let wpkg check if the latest full update is allready 
> installed and then skips the first upgrade command and only installs 
> the fix?
>
Hi,

yes, you can add the condition attribute.
I would add a uninstall check, since that also allows checking for the 
installed version.

'---code start (watch for line wraps)

<upgrade ...>
     <exit ... />

     <condition>
         <check ... />
     </condition>
</upgrade>

'---code end

--
Stefan P.

Top-posting:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?