[wpkg-users] [Bug 79] Major WPKG enhancements, remote logging, doc, internal restructuring
bugzilla-daemon at bugzilla.wpkg.org
bugzilla-daemon at bugzilla.wpkg.org
Tue Nov 20 23:32:43 CET 2007
http://bugzilla.wpkg.org/show_bug.cgi?id=79
Rainer Meier <skybeam at users.sourceforge.net> changed:
What |Removed |Added
Attachment #70 is|0 |1
obsolete| |
--- Comment #56 from Rainer Meier <skybeam at users.sourceforge.net> 2007-11-20 23:32:36 ---
Created an attachment (id=74)
--> (http://bugzilla.wpkg.org/attachment.cgi?id=74)
Full package, /ignoreCase, multiple profiles per host, some fixes
I think you already guess it.... Some more changes to come.
After closing really lots of the bugs within Bugzilla I was working on the last
ones remaining.
As proposed by Falko I moved the change log from wpkg.js header to a standalone
file: Changelog.
CHANGES have been updated as well.
Here's the Changelog for this release:
Changes 2007-11-20, v0.10.12 by Rainer Meier <skybeam (at)
users.sourceforge.net>
NEW: Added /ignoreCase switch which allows to disable case sensitivity of
packages and profiles. Therefore you can assign the package "myapp" to
a
profile while only a package "MyApp" is defined within the packages.
Note that this change requires modifying of the package/profile/host
nodes
read from the XML files. All IDs are converted to lowercase.
Please note that this is a kind of one-way switch. Removing the switch
later will cause all packages which use uppercase characters to fail
looking up the local package node (which is stored in lowercase only).
Fixes Bug 81.
NEW: Implemented change to allow multiple profiles to be specified within a
host node (hosts.xml). The entries need to have the following format:
<host name='hostname' profile-id='main-profile'>
<profile id='profile1' />
<profile id='profile2' />
</host>
The legacy "profile-id" is still used and preferred if you refer just
to one single profile. However it is required to specify at least one
valid profile which can be resolved within profiles.xml.
WPKG will quit immediately if no profile can be resolved. Note that
host definitions in the form of
<host name='hostname' profile-id='main-profile' />
are still allowed and preferred. Additionally the following is allowed
as well:
<host name='hostname'>
<profile id='profile1' />
<profile id='profile2' />
</host>
as long as at least one valid profile is referenced.
Please note: If you use [PROFILE] within the logfile-template the
names
of all referenced profiles are concatenated in the form of
<profile>[-profile[-profile]]
Fixes Bug 53.
FIX: I noticed that I broke the code (again) that config.xml is entirely
optional. As I added a parameter (/config:<path>) to specify the
config
file I decided that WPKG quits in case /config is used but the file
cannot be found (assuming that you know what you're doing and there is
probably something else going wrong so it's better to abort.
In case /config is not used WPKG will not exit if config.xml cannot be
located within the wpkg.js directory.
In case of parsing errors it will quit immediately in any case.
MOD: Revised install procedure regarding the "execute" attribute of the
package. Previously all pacakges were installed as if the execute
attribute would have been set to "once" in pre-0.10.x releases.
This means that packages with no execute flag were not checked at
each run. This has been modified now. The execute flag has three
states now:
"always":
No checks are executed. The package is installed no matter
what
its current install status is.
"once":
The package is installed once to the system and added to local
settings database (wpkg.xml). If the package is within the
local
database it is checked if there is an upgrade available which
will
be installed. If no update is available the package is
skipped.
There are no checks executed to verify that the package is
still
installed. So this is faster than executing the checks but
there is
no verification of the install state done on each synchronize
unless the /force switch is used which forces reinstalling
even if
the package has been installed already once.
any other value (including missing attribute):
The package is verified to be installed even if the package is
within the local package database (wpkg.xml) which indicates
that
the package has been successfully installed once. This allows
to
actually verify the install state on each synchronize.
If the checks yield true (package installed) and no new
package
version is available then the package is skipped (unless
/force has
been specified).
MOD: Improved error handling in case a referenced profile does not exist.
Prints error and continues.
==============================================================================
So this release mainly adresses Bug 81 and Bug 53 which I am going to mark as
fixed now.
WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING
For the changes to take the execute=once attribute correctly into account I had
to touch one of the most complex functions (installPackage()). It's quite late
now and I just did some test using the test suite provided by Falko. Of course
I consider it to be stable - but for the programmer it usually works while it
might fail for others... you know the story...
So it would be very nice if some of you could run some tests as well. I guess
Falko will but I think it's not fair to always rely on one person to do the
full job. So please contribute if you can.
WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING
Finally a list of fixed Bugzilla reports:
Bugs fixed:
Bug 5
Bug 12
Bug 29
Bug 40
Bug 52
Bug 53
Bug 57
Bug 81
(I hope it's complete ;-)
Find more information about all changes within the included CHANGES file.
--
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 at lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
More information about the wpkg-users
mailing list