[wpkg-users] Orphaned packages (patches, settings and service packs)

[Mike Moynihan]

I have several packages that look like this:

<package id="abc" name="abc" priority="105">
    <check ..../>
    <install cmd .... />
    <remove cmd..../>
</package>
<package id="abc-sp1" name="abc-sp1" priority="104">

    <check ..../>    <install cmd .... />
</package><package id="abc-sp2" name="abc-sp2" priority="103">

    <check ..../>    <install cmd .... />
</package>

My question is when I remove package "abc" from a system that has both sp1 and sp2 installed, the packages for sp1 and sp2 remain in the client wpkg.xml file.  The problem is that the removal is based on package "abc".

Once I remove "abc" and it's sp's from the profile, and the wpkg.xml from the client is stripped of the primary package "abc", I find that every time wpkg.js runs, it checks both sp1 and sp2 packages and reports that it can not remove them.

How do I get wpkg.js to remove these orphaned packages?
 
<img alt="Image hosted by Photobucket.com" src="http://i33.photobucket.com/albums/d84/moymike/cb01a160gif.gif">


      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20090504/911139c2/attachment-0001.html>