As far as I understand it, wpkg would inherently do what you want. Once p_1, p_2 and p_3 are all managed packages (i.e., added to wpkg.xml), future runs of wpkg would look at the profile. As long as p_1 is in the profile, all three packages remain (p_1 because it is explicitly listed, and p_2 and p_3 because they are dependencies).
When you remove p_1 from the profile, wpkg would not find any of the three packages mentioned in the profile, but still find them in wpkg.xml. Thus it will then remove these packages. Or maybe I'm mistaken about this. From: wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users-boun...@lists.wpkg.org] On Behalf Of Andy Welch Sent: Thursday, October 14, 2010 7:00 PM To: wpkg-users@lists.wpkg.org Subject: [wpkg-users] Question: chained removals ? Hi all If p_1 is uninstalled, can I cause the prerequisistes p_2 and p_3 to be uninstalled also if no other package depends on them? <package id="p_1"> <depends package-id="p_2" /> <depends package-id="p_3" /> <install cmd="blah blah" /> <remove cmd="moo moo" /> </package> How about the following:- <package id="p_1"> <depends package-id="p_2" chainremove="yes" /> <depends package-id="p_3" chainremove="yes" /> <install cmd="blah blah" /> <remove cmd="moo moo" /> </package> This would require the application being 'aware' that packages "p_2" and "p_3" are no longer prerequisites for any other package - I'll take a look at wpkg.js to see if this is supported. Is there any other way to achieve this? Thx Andy Welch.
------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
