<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><DIV></DIV>
<DIV>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">
<DIV>I understand that these orphaned packages would be removed from the client, if I remove them entirely from the host. But, this only works if I am actually removing the <SPAN class=yshortcuts id=lw_1241457022_0 style="CURSOR: hand; BORDER-BOTTOM: #0066cc 1px dashed">software package</SPAN> entirely from wpkg control.</DIV>
<DIV> </DIV>
<DIV>In my case, I am wishing to remove say... Microsoft Office from all machines within a group. I currently have an SP3 package and a few tweak packages. I have them as separate packages to ensure that they "check" and install as needed. Neither of them have a separate uninstaller, and when the primary package, Microsoft Office, is removed, all that was installed by the add on packages get removed also. This leaves the add on package orphaned.</DIV>
<DIV> </DIV>
<DIV>I do not want to remove the Microsoft Office package from my main package list, as I have many other hosts that contain it in their profiles. I can not run "remove" for these orphaned packages, and it would not work anyways, since each "check" portions fails.</DIV>
<DIV> </DIV>
<DIV>Every time I run WPKG.js on these machines, these "check"s are performed, and these packages are left orphaned in the client wpkg.xml.</DIV>
<DIV> </DIV>
<DIV>I have thought about doing a revision of these, but since they are in use by other clients to wpkg, I have to keep the "check" and the installer the same. Putting in a dummy remove doesn't help, since the check fails for the orphans.</DIV>
<DIV> </DIV>
<DIV>I could edit the wpkg.xml on each client, but I would hope there is a better way to clear these. Am I missing a way to clear these orphaned packages that already works?<BR></DIV>
<DIV>I have some ideas for wpkg.js mods, but wanted to see if there was a current way to handle this issue before I go there.</DIV>
<DIV> </DIV>
<DIV><img alt="Image hosted by <A href="http://photobucket.com/" target=_blank><SPAN class=yshortcuts id=lw_1241457022_1><FONT color=#0000ff>Photobucket.com</FONT></SPAN></A>" src="<A href="http://i33.photobucket.com/albums/d84/moymike/cb01a160gif.gif" target=_blank><SPAN class=yshortcuts id=lw_1241457022_2><FONT color=#0000ff>http://i33.photobucket.com/albums/d84/moymike/cb01a160gif.gif</FONT></SPAN></A>"></DIV>
<DIV><BR></DIV>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif"><BR>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: arial, helvetica, sans-serif"><FONT face=Tahoma size=2>
<HR SIZE=1>
<B><SPAN style="FONT-WEIGHT: bold">From:</SPAN></B> Rainer Meier <<SPAN class=yshortcuts id=lw_1241457022_3 style="CURSOR: hand; BORDER-BOTTOM: #0066cc 1px dashed">r.meier@wpkg.org</SPAN>><BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> Mike Moynihan <<SPAN class=yshortcuts id=lw_1241457022_4 style="CURSOR: hand; BORDER-BOTTOM: #0066cc 1px dashed">moymike@yahoo.com</SPAN>><BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B> <SPAN class=yshortcuts id=lw_1241457022_5 style="CURSOR: hand; BORDER-BOTTOM: #0066cc 1px dashed">wpkg-users@lists.wpkg.org</SPAN><BR><B><SPAN style="FONT-WEIGHT: bold">Sent:</SPAN></B> <SPAN class=yshortcuts id=lw_1241457022_6 style="CURSOR: hand; BORDER-BOTTOM: #0066cc 1px dashed">Monday, May 4, 2009 11:13:07 AM</SPAN><BR><B><SPAN style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [wpkg-users] Orphaned packages (patches, settings and <SPAN class=yshortcuts id=lw_1241457022_7 style="CURSOR: hand; BORDER-BOTTOM:
#0066cc 1px dashed">service packs</SPAN>)<BR></FONT><BR>Hi Mike,<BR><BR>Mike Moynihan wrote:<BR>> I have several packages that look like this:<BR>> <BR>> <package id="abc" name="abc" priority="105"><BR>> <check ..../><BR>> <install cmd .... /><BR>> <remove cmd..../><BR>> </package><BR>> <package id="abc-sp1" name="abc-sp1" priority="104"><BR>> <check ..../><BR>> <install cmd .... /><BR>> </package><BR>> <package id="abc-sp2" name="abc-sp2" priority="103"><BR>> <check ..../><BR>> <install cmd .... /><BR>> </package><BR>> <BR>> My question is when I remove package "abc" from a system that has both<BR>> sp1 and sp2 installed, the packages for sp1 and sp2 remain in the client<BR>> wpkg.xml file. The problem is that
the removal is based on package "abc".<BR>> <BR>> Once I remove "abc" and it's sp's from the profile, and the wpkg.xml<BR>> from the client is stripped of the primary package "abc", I find that<BR>> every time wpkg.js runs, it checks both sp1 and sp2 packages and reports<BR>> that it can not remove them.<BR>> <BR>> How do I get wpkg.js to remove these orphaned packages?<BR><BR>There are sevaral ways to achieve this. First of all it seems that you failed to<BR>specify some dependencies between these packages ("abc-sp1" and "abc-sp2" depend<BR>on "abc", maybe "abc-sp2" depends only on "abc-sp1" to create a chain... who<BR>knows...). If you would have done so, then uninstalling "abc" would also remove<BR>packages which depend on it (e.g. "abc-sp1" and "abc-sp2").<BR><BR>Now you end up with en uninstalled "abc" package while the "abc-sp1" and<BR>"abc-sp2" packages still exist and WPKG of course tries to remove them while
the<BR>remove command of these packages might fail.<BR><BR>As long as "abc-sp1" and/or "abc-sp2" are stil part of the package database on<BR>server side (packages.xml) WPKG will re-try to uninstall them properly on each<BR>run. So you still have the chance to fix your "abc-sp1"/"abc-sp2" package<BR>definitions to correctly uninstall even if "abc" has been removed already. To do<BR>so you might just fix the package definition and increase the revision number.<BR>So WPKG will first do an upgrade (using eventually defined upgrade commands) and<BR>then uninstall it - using the new uninstall commands.<BR><BR>In case we are really talking about a <SPAN class=yshortcuts id=lw_1241457022_8>service pack package</SPAN> or similar removing<BR>them might not be required any more. In this case just remove<BR>"abc-sp1"/"abc-sp2" completely from your packages.xml on server side. WPKG will<BR>then try to remove it on client side and even if it fails to do so it
will<BR>remove the package from the local package database. This prevents you from<BR>ending up in an endless remove-loop on each reboot.<BR>So as long as you would like to keep a chance to fix your "abc-sp1"/"abc-sp2"<BR>package you keep it within packages.xml and you might fix it as many times as<BR>you like. As soon as you remove it completely WPKG will try once again to remove<BR>it and then remove it anyway from the local wpkg.xml, thus not re-trying to<BR>remove it on next reboot.<BR><BR>br,<BR>Rainer<BR></DIV></DIV></DIV><BR><SPAN id=lw_beacon_1241457022797></SPAN>
<DIV id=highlighterDivCG style="DISPLAY: none; Z-INDEX: -1; POSITION: absolute; BACKGROUND-COLOR: yellow"></DIV>
<DIV class="module overlay yui-module yui-overlay" id=lwPreview style="LEFT: -400px; POSITION: absolute; TOP: -400px">
<DIV class=hd></DIV>
<DIV class=bd> </DIV>
<DIV class=ft></DIV></DIV></DIV></div><br>
</body></html>