[wpkg-users] [Bug 244] New commands syntax leads to exception

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=244

Rainer Meier <r.meier at wpkg.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |r.meier at wpkg.org
         Resolution|                            |FIXED

--- Comment #3 from Rainer Meier <r.meier at wpkg.org>  ---
Hi Stefan,

I could verify this with WPKG 1.2.1-RC22 and included a fix in RC23 which I've
just commited. I hope nothing went wrong as SVN 1.7 seems to require workspace
migration which took forever and changed lots of files - I really hate this
VCS...


MOD: Modified XSD data structure. Moved common elements to wpkg.xsd in order
     not to duplicate documentation.
FIX: Prevent crash in case of invalid XML wehere a <variable /> node is missing
     either the name or value attribute. WPKG will now print an error to the
     logs and ignore the variable.
     Thanks to Stefan Pendl for reporting. Fixes bug 243.
FIX: Fixed handling of packages which do not use classic commands but only the
     new commands style using <commands /> node.
     Thanks to Stefan Pendl for reporting. Fixes bug 244.
NEW: New feature allowing manual package installation to be combined with
     synchronization.
     If a package is installed manually using the /install:<package> command-
     line switch, then the package is added to the local package database and
     retained during future synchronizations.
     In previous versions of WPKG you could have either installed packages via
     profiles or manually but if you installed a package manually then
     subsequent synchronizations would have removed the package if it was not
     part of the profile. This enhancement allows local administrators to
     manually install any package provided in the package database. Packages
     installed manually will also be updated on subsequent synchronizations.
     Let's provide some examples.

     Host A has the following packages assigned:
     - Pidgin
     - Thunderbird

     A local administrator would like to install Firefox on the machine too.
     Of course as a local admin he could also install Firefox using the Mozilla
     installer but this would mean he has to take care about updates and
     potentially synchronize such update actions with the IT departement.
     Now a local administrator could simply use the "wpkg.js /install:firefox"
     command (of course given the fact that the IT departements maintains a
     package called "firefox") and get the official Firefox package installed.

     On future "wpkg.js /synchronize" runs WPKG will update the "firefox"
     package in the same way as if the IT departement would have added
     "firefox" to the profile applied to the host. Therefore on the host as
     defined above WPKG would look for updates on Pidgin, Thunderbird and
     Firefox during synchronization.


     If the IT departement decides to remove the "firefox" package from the
     server-side package database this likely means that support is dropped and
     Firefox shall not be used any more. In such case WPKG would also remove
     the package manually installed via /install:firefox on synchronization.

     So as you see the /install:<package> switch can be used by local
     administrators to kind of modify or extend the server-based profile with
     some manually chosen packages which keep updated automatically when
     synchronizing.


As usual, get it from here:
<http://wpkg.svn.sourceforge.net/viewvc/wpkg/wpkg/stable/1.2/>

br,
Rainer

-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.