[wpkg-users] [Bug 79] Major WPKG enhancements, remote logging, doc, internal restructuring

bugzilla-daemon at bugzilla.wpkg.org bugzilla-daemon at bugzilla.wpkg.org
Sat Nov 24 01:19:08 CET 2007


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


Rainer Meier <skybeam at users.sourceforge.net> changed:

           What    |Removed                     |Added

  Attachment #74 is|0                           |1
           obsolete|                            |




--- Comment #61 from Rainer Meier <skybeam at users.sourceforge.net>  2007-11-24 01:19:02 ---
Created an attachment (id=75)
 --> (http://bugzilla.wpkg.org/attachment.cgi?id=75)
Full package, added installdata/uninstalldate attribute to profile
package-references

Ho Ho Ho... no, it's not santa-clause but I bring a present along anyway ;-)

It took me a bit longer then planned. Mainly because I focused on parsing the
date/time format as flexible as possible (and programmers know how hard this
can be ;-)

Well, finally I managed to implement the last feature on the TODO list:
Installing/removing a package based on the installdate/uninstalldate attribute
within the profile.

Here are the change notes:
Changes 2007-11-24, v0.10.13 by Rainer Meier <skybeam (at)
users.sourceforge.net>
NEW: Added ability to install packages by date.
         To use this feature an install/uninstall date has to be specified
within
         the package node of the profile. Example:
         <package package-id="pkg" installdate="<date>" uninstalldate="<date>"
/>

         Note that a package can be referenced several times within different
         profiles. Each profile can specify its own install/uninstall date for
a
         specific package (that's why it is not a property of the package
itself).

         In case a host has multiple profiles assigned and the package is
         referenced from multiple profiles WPKG will evaluate all package
         references. If one of the references specify that the package has to
be
         installed (or not date-range is specified at all), the package will be
         applied.

         Date is parsed in ISO 8601 format.
         See <http://www.w3.org/TR/NOTE-datetime>.
         Generic format example:
                "YYYY-MM-DD hh:mm:ss"
         Valid date examples:
                (the following dates are all equal if ceil is set to false)
                "2007-11-23 22:00"                      (22:00 local time)
                "2007-11-23T22:00"                      (Both, "T" and space
delimiter are allowed)
                "2007-11-23 22:00:00"           (specifies seconds which
default to 0 above)
                "2007-11-23 22:00:00.000"       (specifies milliseconds which
default to 0)
         It is allowed to specify the timezone as well:
                "2007-11-23 22:00+01:00"        (22:00 CET)
                "2007-11-23 21:00Z"                     (21:00 UTC/GMT = 22:00
CET)
                "2007-11-23 22:00+00:00"        (21:00 UTC/GMT = 22:00 CET)

         If 'ceil' is set to true then unspecified date components do not fall
back
         to "floor" (basically 0) but will be extended to the next value.
         This allows easy comparison if the current date is within a parsed
"!ceil"
         date and a parsed "ceil" date.
         Examples:
         ceil=false:
                "2007-11-23"    => "2007-11-23 00:00:00"
                "2007-11"               => "2007-11-01 00:00:00"
         ceil=true:
                "2007-11-23"    => "2007-11-24 00:00:00"
                "2007-11"               => "2007-12-01 00:00:00"

         TIMEZONES:
         As specified by ISO 8601 the date is parsed as local date in case no
         time zone is specified. If you define a time zone then the specified
time
         is parsed as local time for the given time zone. So if you specify
         "2007-11-23 22:00+05:00" this will be equal to "2007-11-23
18:00+01:00"
         while "+01:00" is known as CET as well. The special identifier "Z" is
equal
         to "+00:00" time zone offset.

         Usually you will not specify any time zone at all since you might have
a
         package installed at 08:00 local time rather than installing it at
         08:00 in UTC+1 time zone while it is installed at 15:00 in UTC+8 time
         zone (when specifying 07:00Z or 07:00+00:00 install time).

         Specifying an empty string as dateString is allowed and will results
in
         returning the first of january 00:00 of the current year (ceil=false)
or
         first of january 0:00 of the next year (ceil=true).

         This implements a feature on the TODO list.
MOD: Ordered functions by name and group (functionality, logging,
supplementary).



enjoy.


-- 
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