http://bugzilla.wpkg.org/show_bug.cgi?id=95
Rainer Meier <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[EMAIL PROTECTED]
| |t
--- Comment #6 from Rainer Meier <[EMAIL PROTECTED]> 2008-01-14 20:55:29 ---
For package downgrade there is - at least for almost all packages - a simple
solution. Just increase the package version within the XML definition again and
make sure the upgrade procedure will properly handle the downgrade.
Note that the package version does not have to be equal to the software
version. This is even not possible most of the time because the package version
is an integer value while most software uses dotted x.y.z version number.
OK, I know that I introduced the possibility to use x.y.z within the package
version as well. But still you can increase the package version and declare it
as a "new" fixed version.
On the other side it would be possible to implement such downgrade commands.
But I have some doubts that this would be a frequently used functionality at
the cost of added complexity.
--
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
