[wpkg-users] [Bug 94] /remove should remove dependend packages and/or profiles
http://bugzilla.wpkg.org/show_bug.cgi?id=94 Rainer Meier <[EMAIL PROTECTED]> changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #8 from Rainer Meier <[EMAIL PROTECTED]> 2008-02-18 10:35:12 --- No feedback yet. Seems to work. Closing bug. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Do you use WPKG? Tell us how! >> http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 94] /remove should remove dependend packages and/or profiles
http://bugzilla.wpkg.org/show_bug.cgi?id=94 Rainer Meier <[EMAIL PROTECTED]> changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Comment #7 from Rainer Meier <[EMAIL PROTECTED]> 2008-01-14 21:40:13 --- Setting to "fixed" in the hope that it it working from scratch - if not we will just fix the problems but the basic changes are already implemented. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Do you use WPKG? Tell us how! >> http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 94] /remove should remove dependend packages and/or profiles
http://bugzilla.wpkg.org/show_bug.cgi?id=94 --- Comment #6 from Rainer Meier <[EMAIL PROTECTED]> 2008-01-14 21:38:14 --- Created an attachment (id=96) --> (http://bugzilla.wpkg.org/attachment.cgi?id=96) Dependency tree removal OK, as described within Bug 55 we are not going to implement any more change requests or enhancements to the 1.0 release. So I created a new "Milestone" release (1.1-M1). From now on I will start to implement changes/enhancement within this version. Only major bugfixes will still be done in 1.0. This allows 1.0 to be used as a stable release. So here's the first 1.1 pre-release including recursive dependency removal. Please note: Also this release has not been tested yet. It has been written on-the-fly*. I will test it when I am back at home. Probably you can do that already in the meantime. * Which really means what I wrote, written in the airplane from Zurich to Warsaw ;-) Changes: NEW: removePackage now removes all packages which depends on the one to be removed as well (recursively). This assures that after poackage uninstall no packages are left installed which miss their required dependency. Please note that if a package which depends on the one to be removed specifies an immediate reboot the reboot takes place right after the this package has been removed. In such case the package initially requested to be removed will still be there after the reboot. To avoid this it is possible that depending packages use the postponed reboot functionality. Alternatively you can use the /noreboot switch to advice WPKG to ignore each reboot request. Note that in such cases some packages will not properly finish their uninstall procedure. In case removing of any package from the dependency tree fails WPKG will stop uninstalling and print a message. In such case the package you requested to remove will still be there because there is at least one more package which depends on it. You can advice WPKG to remove the requested package in any case by using the /force switch. Warning: In such case it might happen that some packages depending on the removed one could not be removed and therefore will be left on the system (probably not working any more). -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Do you use WPKG? Tell us how! >> http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 94] /remove should remove dependend packages and/or profiles
http://bugzilla.wpkg.org/show_bug.cgi?id=94 --- Comment #5 from Rainer Meier <[EMAIL PROTECTED]> 2008-01-11 20:52:46 --- Just a status update... I did not forget about that change. However proper implementation and test requires some time. There are numerous use-cases and variations (remove, synchronize, with or without forcing) which have to be taken into account. My highest priority is to make sure that no matter what you do it will not break automatic synchronization - which will most probably run on next startup. Therefore (and because this feature is not critically rated from my point of view) I focus on proper implementation and quality instead of quick and dirty solution. I am quite short on sparetime currently but I think I can promise something within the next 7 days. I hope that's fine. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Easy Software Deployment >> http://wpkg.org ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 94] /remove should remove dependend packages and/or profiles
http://bugzilla.wpkg.org/show_bug.cgi?id=94 Rainer Meier <[EMAIL PROTECTED]> changed: What|Removed |Added CC||[EMAIL PROTECTED] ||t Status|NEW |ASSIGNED --- Comment #4 from Rainer Meier <[EMAIL PROTECTED]> 2008-01-08 23:30:23 --- I see that a dependency-aware removal could be helpful. However it is only useful in case of manual package handling (i.e. manual removal). Automatic handling (synchronization) already takes care about the dependencies (at least at installation). However reverse-dependencies are a bit harder to trace. Remember that we do not have to trace the package dependencies (i.e. the package which the package to be removed depends on) but the packages which depend on the one to be removed. This could lead to a whole tree of packages being removed when removing a single package (all packages which depend on the one requested to be removed or any of the packages selected by recursion). I even think this would not be too much complicated since I even will not have to track "limit" the number of uninstalled packages. WPKG can simply remove all packages depending on the one to be removed or the one depending on these packages... (recursively). Of course this could break away quite a huge part of the package tree when removing an important package but installation/synchronization will immediately re-install it as soon as the package check of any package depending on the manually removed shows that the dependency is not installed any more. I also think that there should be no additional /deps switch due to two reasons: - If a package depends on one to be removed then it can be assumed that it will NOT run without it at all. So it's safe to remove it. Even packages depending on that 2nd level package will most probably fail to work after that so it's safe to remove them as well. In case a package dependency is "optional" then nobody would specify a hard dependency but just add the packages one-by-one to the profile. - Using another /deps switch will increase complexity and most users will not use it at first try (because nobody will look for such a switch in advance). With the result that the dependencies are usually not removed. Once the removal has been executed there is no way to re-execute it without re-installing and another manual uninstall invocation. In worst case I would introduce a /nodeps switch but I don't like this idea because it can lead to broken dependency structures by removing a package which is required by others - and this is exactly what this patch is going to fix. So let me think about... I will think about the implementation. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Easy Software Deployment >> http://wpkg.org ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 94] /remove should remove dependend packages and/or profiles
http://bugzilla.wpkg.org/show_bug.cgi?id=94 --- Comment #3 from Falko Trojahn <[EMAIL PROTECTED]> 2007-12-17 17:06:18 --- #1 I think /remove /deps is a good idea. As it is just for testing, it's of course not so important to have, but convenient. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Easy Software Deployment >> http://wpkg.org ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 94] /remove should remove dependend packages and/or profiles
http://bugzilla.wpkg.org/show_bug.cgi?id=94 --- Comment #2 from Jens Geile <[EMAIL PROTECTED]> 2007-12-17 10:41:54 --- I think /remove should be enough to remove a package and all its dependencies _UNLESS_ another package has the same dependency. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Easy Software Deployment >> http://wpkg.org ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 94] /remove should remove dependend packages and/or profiles
http://bugzilla.wpkg.org/show_bug.cgi?id=94 --- Comment #1 from Tomasz Chmielewski <[EMAIL PROTECTED]> 2007-12-17 10:40:18 --- Or, should it throw an error and say "Firefox depends on plugin_A, plugin_B: use /force to remove without dependencies, or /deps to remove with dependencies."? -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Easy Software Deployment >> http://wpkg.org ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
