http://bugzilla.wpkg.org/show_bug.cgi?id=95 Rainer Meier <r.meier at wpkg.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #8 from Rainer Meier <r.meier at wpkg.org> 2008-02-25 22:44:46 --- OK, this is an enhancement which can be considered for future versions (1.1?) but will definitely not be included in 1.0 release (feature-freeze). I will think about it. Actually the change will be pretty easy to do I believe but I currently have some doubts that it is really required. On the other hand it could create some confusion for example if the administrator sets a wrong version number (which is numerically less than the previous one) while thinking it will do an upgrade. I personally try to crate an integer value from the full version number of an application. For example 1.2.60 becomes 1260. Unfortunately the third number has two digits. So the next version (for example 1.3.1) has to become 1301 to be numerically larger than the first one. Using "131" as a version number would execute the downgrade command in this case which will probably not work. With the current implementation WPKG will simply print a message and ignore the (presumably older) package. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |