[EMAIL PROTECTED] schrieb:
Hello there.
Wpkg 0.9-test2 contains an error.
in File "wpkg.js" Function "notify(message)" exists twice. (line 1790 and
line 1809)
Quick workaround:
remove the slash on line 1808. This will Comment the old function out.
(Tomasz simply forgot to remove the old function)
yeah I noticed it doesn't work as it should :(
in fact the notifying doesn't work with XP SP2 at all, even though
enabled, and that's why I thought /nonotify works.
http://support.microsoft.com/default.aspx?scid=kb;en-us;839018
maybe we should remove this whole notifying anyway? is anyone actually
using it? I got the impression that it's only annoying :)
----------------------
Another theme:
I can implement the "Installing and UnInstalling on a certain date" as a
checkCondition.
that'd be nice :)
thinking about it, there do arise some questions:
1. what for is this?
mainly it would be useful in schools / universities / other
organisations that make courses, seminars etc.
sometimes software is only needed for the duration of some course.
so an admin could schedule the software to be installed on certain date,
go on holiday, and not worry about anything - well, perhaps he made a
typo, so the software won't install anyway :))
some software could have "install date" only; some could have "uninstall
date" only (for example, from this and that date we will remove software
X and Y, as it is obsolete, or beta has expired, or we were running a
30-day test version etc.).
2. should the user get an information "not installed because of
installdate-restriction" or not?
hmm, maybe if run in the /debug mode?
"skipped, not installed because of installdate-restriction (aa.bb.cccc)".
3. the script does not run on "uninstall-date" (due to a power loss or so),
now the package keeps installed?
no, it should be removed.
for example, suppose we have "installdate = 15.06.2005", and
"uninstalldate = 30.10.2005".
even though the computer was turned off the whole 06, 07 and 08 month,
the software should be installed, if:
- the install date is today or later, and
- we didn't reach the uninstall date
same should go for uninstalling.
if the uninstalldate was 30.10.2005, but it's Sunday, and the PC was
off, the software should be removed if the uninstalldate is today or later.
4. (coming from 3.) is "installdate" first day if install-ability?
first day, or any later, no later than uninstalldate ("uninstalldate" is
not obligatory)
5. (coming from 3.) is "uninstalldate" first day if uninstallation?
first day, or any later, no earlier than installdate (again,
"installdate" is not obligatory, we may only want to uninstall something
on a certain date)
6. which clock do we trust?
Only CERN, the European Organization for Nuclear Research, the particle
physics laboratory, located in Geneva, Switzerland is worth trust :)
I think it should be the client's clock, as is is usually synced to that
of the server, and even if it's not synced, the date should be the same.
We should stick to the client, it's administrator's role to keep the
time in sync.
--
Tomek
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
wpkg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wpkg-users
