[wpkg-users] [Bug 103] Handling absence of config.xml
http://bugzilla.wpkg.org/show_bug.cgi?id=103 Rainer Meier [EMAIL PROTECTED] changed: What|Removed |Added Attachment #99 is|0 |1 obsolete|| --- Comment #1 from Rainer Meier [EMAIL PROTECTED] 2008-02-18 09:19:42 --- Created an attachment (id=101) -- (http://bugzilla.wpkg.org/attachment.cgi?id=101) Full package, fixed for bug 103 and 104 OK, the facts here might be a little more complicated than you might think actually. You are right that in the current implementation nothing is printed in case config.xml is missing. However WPKG is fully operational even completely without config.xml. But... When the /quiet parameter is specified OR config.xml contains quiet=true parameter WPKG should never ever print any line (but write to event log). When your change is applied then WPKG will print any message logged during initialization to the console window. Even if /quiet or the quiet parameter within config.xml is set it will print some lines which is completely against the intention of the /quiet parameter. Therefore the implementation was made in such a way that WPKG always operates in quiet mode during initialization. As soon as the real quiet mode could be evaluated (after reading config.xml and parsing the command line parameters) quiet mode could be switched off. Unfortunately you're right in one thing. The /help screen does not show up if config.xml is missing (it is logged to event log instead). I consider this to be Bug 103.1. Additionally WPKG yields a null-pointer exception during initialization which is logged to event log. I consider this to be Bug 103.2. A fix for both issues is included in the attached WPKG 1.0 RC8. The implementation slightly differs from your proposal. Instead of handling possible null-pointer return values on various locations I just make sure that getConfig() does return a valid XML node in any case which fixes all null-pointer problems at once. Now also the help screen shows up properly. Again: I consider it to be a bad idea to disable quiet mode during initialization because this might lead to undesired user-notifications during initialization even if the /quiet flag and/or the quiet parameter is set. Changes: Change notes WPKG Version: 1.0-RC8 Author: : Rainer Meier skybeam (at) users.sourceforge.net Date: 2008-02-18 Changes/fixes visible to the user: Summary: - Fixed missing quote in log output FIX: Included cosmetic fix for Bug 104 (opening quotation missing). This fix adds a missing opening quotation in debug output when a new package is added to the local settings node (after installation success). FIX: Fixed Bug 103. /help screen is not showing up if config.xml is missing and null-pointer exception is thrown. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 103] Handling absence of config.xml
http://bugzilla.wpkg.org/show_bug.cgi?id=103 Rainer Meier [EMAIL PROTECTED] changed: What|Removed |Added Attachment #102 is|0 |1 obsolete|| --- Comment #4 from Rainer Meier [EMAIL PROTECTED] 2008-02-18 09:40:53 --- Created an attachment (id=104) -- (http://bugzilla.wpkg.org/attachment.cgi?id=104) Full package, fixed for bug 103 and 104 - changes for 1.1 milestone release Sorry, during diff I recognized a small coding inconsistency. Not a bug but I would like it to be done consistently... Please use the updated version attached. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 104] (Trivial absence of opening quote in Adding settings node)
http://bugzilla.wpkg.org/show_bug.cgi?id=104 Rainer Meier [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #2 from Rainer Meier [EMAIL PROTECTED] 2008-02-18 09:44:32 --- Closed - as fix is included in RC8 to be released soon. See Bug 103 -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 42] add a time parameter
http://bugzilla.wpkg.org/show_bug.cgi?id=42 Rainer Meier [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #18 from Rainer Meier [EMAIL PROTECTED] 2008-02-18 10:32:30 --- OK, I think I will carefully think about a flexible way to extend WPKG to allow WPKG GUI to display some progress. I am still completely unconvinced that any estimated time to finish should be generated by WPKG since it adds far too much complexity while chances to provide any usable and reliable information are extremely low. I think about implementing a first draft within WPKG 1.1 pre-release branch. Please be patient since proper design will definitely need some time. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 96] Crash/ exception when checking the value of a non-existent registry entry
http://bugzilla.wpkg.org/show_bug.cgi?id=96 Rainer Meier [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #5 from Rainer Meier [EMAIL PROTECTED] 2008-02-18 10:33:59 --- No feedback yet. Seems to work properly. Closing bug. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 94] /remove should remove dependend packages and/or profiles
http://bugzilla.wpkg.org/show_bug.cgi?id=94 Rainer Meier [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #8 from Rainer Meier [EMAIL PROTECTED] 2008-02-18 10:35:12 --- No feedback yet. Seems to work. Closing bug. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Logging enhancement request
grubi -- 16.02.2008 15:39: Hi Florian, You could add the date to the filename, see config.xml for details. That is what we already did. Currently we have [HOSTNAME]-[]-[MM]-[DD] which of course do not prevent the log to be overwritten during necessary reboots. Sure we could also add [mm] and [ss] to prevent this but then the whole installation process of one machine would be spread among multiple logs which is also not very pleasent. That beeing said I'm still convinced that having a setting like AppendToLogFile=Yes/no would not be that bad. There has been much discussion about that on the list already. To have something like this (you can call it log rotation) I just use [HOSTNAME]-[mm].log and sort the log directory by time. So I get all the log files, containing the whole installation process. There is not much propability that the files get overwritten too soon. Falko - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
[wpkg-users] [Bug 92] Enhanced Logging
http://bugzilla.wpkg.org/show_bug.cgi?id=92 Rainer Meier [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #31 from Rainer Meier [EMAIL PROTECTED] 2008-02-18 10:38:18 --- #30: I don't agree that any further extensions should only print to debug out. Especially if we would introduce multiple debug levels (which one will be the default one then?). I could already imagine the discussions here. So I am closing the discussion for now until we are discussing about a completely different way of logging. Closed. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug. - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] Logging enhancement request
Hi Falko. There has been much discussion about that on the list already. To have something like this (you can call it log rotation) I just use [HOSTNAME]-[mm].log and sort the log directory by time. So I get all the log files, containing the whole installation process. There is not much propability that the files get overwritten too soon. No sure if it is a good idea to integarte log rotation directly into wpkg. This one could easily be done by regularily scheduling a simple jscript deleting all files older than a specific date. Additionally you could also do things like packing old logs and move them to a different location. This approach reduces complexity of wpkg and still gives you all the flexibility you need. However what IMHO is still missing is the flexibility to specify that logs are appended and not overwritten. If you look at other apps you will find that appending to logs it the most often default behavour for logging because this ensures that no important information gets lost. Just my 2 cents. grubi. - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] %SOFTWARE% variable
Hi Marc Marc Cuypers wrote: In the silent installs the variable %SOFTWARE% is used. I tried to set it with the wpkg-client (general/wpkg variable). But it seems not to be expanded. Is there a problem with this expansion. No, no known problem with the expansion and I use this feature daily. You just need to define the SOFTWARE variable within WPKG-client. Do not specify the % sign within the specification. Just add a variable called SOFTWARE pointing to the share used \\server\share. So check the variable definition that you do NOT include any % signs and check for typos. Second question: Where does the wpkg-client save its configuration data? This can be answered by some WPKG client developers ;-) HTH Rainer - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
Re: [wpkg-users] %SOFTWARE% variable
Hi all, I also was confused, because variables defined in wpkg-client are not expanded, if you test your installation from the command line manually with /debug flag. So I think for testing/debugging packages with variables defined in the client one has to use the wpkg-client and set Show in Script user interface. Gerd Hi Marc Marc Cuypers wrote: In the silent installs the variable %SOFTWARE% is used. I tried to set it with the wpkg-client (general/wpkg variable). But it seems not to be expanded. Is there a problem with this expansion. No, no known problem with the expansion and I use this feature daily. You just need to define the SOFTWARE variable within WPKG-client. Do not specify the % sign within the specification. Just add a variable called SOFTWARE pointing to the share used \\server\share. So check the variable definition that you do NOT include any % signs and check for typos. Second question: Where does the wpkg-client save its configuration data? This can be answered by some WPKG client developers ;-) HTH Rainer - Do you use WPKG? Tell us how! http://wpkg.org/Testimonials ___ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
