http://bugzilla.wpkg.org/show_bug.cgi?id=55 Thomas Bøge <thomas at boegenielsen.dk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas at boegenielsen.dk --- Comment #4 from Thomas Bøge <thomas at boegenielsen.dk> 2007-12-11 16:14:18 --- I guess I have not explaint why I would like the (poosibly unclean implementation of) /noremove feature. I am using wpkg to both fully managed workstations and "partly managed". I fully agree, that there is no need for /noremove for fully managed workstations. With "partly managed" I mean workstations, configured and managed by end-users (powerusers), where I provide an easy way to install a subset of all my packages, represented by a certain profile. Since powerusers don't like that software is removed without their accept, but need an easy way to install a lot of common software, /noremove is an ideal solution for me. I realise, that I could make copies of all my packages, rename them and remove <remove...> and change execute to once. But that would almost double my work with maintaining packages. I am not a trained user of bugzilla, so don't know if it good behavior to reopen this feature-request with only 1 vote. But anyway, please reconsider "wontfix" -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. -------------- next part -------------- ------------------------------------------------------------------------- just about anything Open Source. http://sourceforge.net/services/buy/index.php -------------- next part -------------- ------------------------------------------------------- Easy Software Deployment >> http://wpkg.org _______________________________________________ wpkg-users mailing list wpkg-users at lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users |