One alternative would be to slipstream all of your Office updates into
your office install point. Not sure if that would be more work or not,
but it should go faster. 

-----Original Message-----
From: Jens Geile [mailto:[EMAIL PROTECTED] 
Sent: Thursday, August 04, 2005 7:57 AM
To: [email protected]
Subject: [wpkg-users] Feature Request

Hi,

been some time since I last had the chance to do some work on my
unattended+wpkg setup but this thing here is really bugging me and I
would _really_ like it to be implemented since it would make things _a
lot_ easier for all of us.

A current package entry would look something like this:

<package
    id="whatever"
    name="Whatever package"
    revision="1"
    reboot="false"
    priority="0">

    <check type="registry" condition="exists" path="HKLM\whatever" />
    <check type="file" condition="exists" path="C:\whatever.exe" />
    <check type="uninstall" condition="exists" path="Whatever Package"
/>
        
    <install cmd='msiexec /i (path to msi)'>
        <exit code="0" />
    </install>
    <remove  cmd='msiexec /x (path to msi)' />
    <upgrade cmd='msiexec /i (path to msi)' /> </package>

Now imagine you'd like to install Microsoft Office 2003 for example. How
would you install all the updates and make sure each update is only
installed once (read keep track which update was already installed)? Add
one package for each update? How about when you want to have the ability
to install either Microsoft Office 2000, XP or 2003? How about all the
updates then? Adding a package for each update would easily result in
100+ packages for Office updates only and it would be hell to keep
everything up2date.

So here is my idea:
We need something for installing updates. Maybe something like this?

<package
   id="whatever"
   name="Whatever package"
   revision="1"
   reboot="false"
   priority="0">

   <check type="registry" condition="exists" path="HKLM\whatever" />
   <check type="file" condition="exists" path="C:\whatever.exe" />
   <check type="uninstall" condition="exists" path="Whatever Package" />
        
   <install cmd='msiexec /i (path to msi)'>
       <exit code="0" />
   </install>

    <updates>
       <update id="KB8102002" name="Whatever update KB8102002"
       revision="1" reboot="false" priority="0">
           <check type="registry" condition="exists"
path="HKLM\whatever\blubb" \>
           <install cmd='msiexec /i (path to msi)'>
              <exit code="0" />
           </install>
       </update>

       <update id="KB2234175" name="Whatever update KB2234175"
       revision="1" reboot="true" priority="0">
           <check type="registry" condition="exists"
path="HKLM\whatever\blubb2" \>
           <install cmd='msiexec /i (path to msi)'>
              <exit code="0" />
           </install>
       </update>
    </updates>

    <remove  cmd='msiexec /x (path to msi)' />
    <upgrade cmd='msiexec /i (path to msi)' /> </package>

The list of updates should be executed from first to last (FIFO) so that
new updates can easily be added at the end of the list.

Why I'm asking for this? Because I'd like to use WPKG for all my
software installations and that would include Microsoft Office.
Installing Office with unattended works (more or less) but there is
currently no way for me to deploy updates for either Windows or Office.
With this feature it would be easy to deploy both Windows and Office
updates (not to mention all the updates for other software packages). :)

Any suggestions? Objections?

I'd add this feature myself and supply a patch but my JavaScript
skills... to put it simple .. suck. ;) But I'd still like to see this
added sometime. :]


On a side-note: I've been idling on irc.irchighway.net in the channel
#wpkg but sadly missed Tomek today. So if anyone feels like talking
about WPKG feel free to visit.
My nick would be "worf" and if I'm not around or not answering right
away just idle there and I'll come by every now and then if my time
allows me too.

-
jens


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices Agile & Plan-Driven Development * Managing Projects & Teams *
Testing & QA Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
_______________________________________________
wpkg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wpkg-users




-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
wpkg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wpkg-users

Reply via email to