http://bugzilla.wpkg.org/show_bug.cgi?id=120 Summary: Enhanced revision check and handling Product: WPKG Version: 1.0.2 Platform: PC OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: wpkg.js AssignedTo: mangoo at wpkg.org ReportedBy: jens.geile at mzbs.de QAContact: wpkg-users at lists.wpkg.org Ok, another feature request from me.. Today I ran into a little problem when I wanted to update a package that was already installed on a couple of machines. In this case it was OpenOffice which I installed but forgot to link .doc/.xls/.ppt files to it. I though: "No problem, just write an appropriate upgrade command upgrade OpenOffice by increasing the revision of the package." The problem here: It didn't work. Why? Because the revision of the installed package was 2.4.0 (OpenOffice version) and the revision of the updated package was 2.4.0.1! I thought that WPKG would be smart enough and detect that the revision 2.4.0.1 is GREATER than 2.4.0 but obviously it isn't. WPKG just did nothing. No upgrade, no nothing. It didn't even upgrade the local wpkg.xml with the new package. What's my actual request? Why not use the debian version control system as documented on http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version ? Its far superior to the current system if you ask me. Yes, I could of course use "revision='1'" -> "revision='2'" -> "revision='3'" but this is really not what anyone should want. Using the version of the software to be installed as the revision of the package would be ideal and is what I'm already doing for all my packages. If you were able to use "revision='2.4.0-0'" -> "revision='2.4.0-1'" like you are when using .deb packages under debian WPKG would be one step closer to being perfect. ;) -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |