http://bugzilla.wpkg.org/show_bug.cgi?id=177 Summary: Local install flag Product: WPKG Version: 1.1.2 Platform: PC OS/Version: Windows XP Status: NEW Severity: enhancement Priority: P2 Component: wpkg.js AssignedTo: r.meier at wpkg.org ReportedBy: ftrojahn at smi-softmark.de QAContact: wpkg-users at lists.wpkg.org Some time ago I missed the feature of packages marked as "locally installed", which came to my mind again as a possible solution for bug 175, so I'll try to explain that here. Preference: "wpkg.js /install:<package name>" does install a package locally, "wpkg.js /remove:<package name> does remove that same package. Problem: But wpkg.js /synchronize does - logically - remove all packages which are not in hosts/profiles database. So, locally installed packages are automagically removed from the system as intended. Sometimes, e.g. for testing reasons or to give a special user the possibility to install a package himself, I think it would be essential to have a manually installed package not automagically removed from the system when synchronizing. Solution: "wpkg.js /install:<package name> /local" or "wpkg.js /install:<package name> /persistent" marks a package in local wpkg.xml as <package id='Firefox' name='Mozilla Firefox' revision='3.5.0' priority='50' reboot='false' local='true'> ... </package> or <package id='Firefox' name='Mozilla Firefox' revision='3.5.0' priority='50' reboot='false' persistent='true'> ... </package> For the difference between "local" and "persistent" I could imagine that for "local" packages the usual upgrade mechanism of wpkg.js /synchronize is used, but "persistent" packages never upgrade automagically, so I can have a system with a special revision of a package until I upgrade this system manually or the package is assigned to this host by hosts.xml/profiles.xml. Keep up with your good work! Regards, Falko -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |