<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
<BR>> Date: Mon, 19 Oct 2009 13:16:46 +0200<BR>> From: ralf.lederle@ite.uni-stuttgart.de<BR>> To: wpkg-users@lists.wpkg.org<BR>> Subject: [wpkg-users] Suggestion: upgrades from specific revisions<BR>> <BR>> Hi,<BR>> <BR>> I think it would be a good thing, if you could define different upgrade<BR>> commands for upgrades from specific revisions.<BR>> <BR>> For example: if you actually want to upgrade Adobe Acrobat 9, you first need<BR>> to uninstall it, install it again and then apply 4 patches, which takes quite<BR>> a lot of time. On machines, where the actual revision is installed, applying<BR>> only one new patch would be sufficient.<BR>> <BR>> I have something in mind like this:<BR>> <BR>> <upgrade fromrevisionlessthan="5" cmd="..."/><BR>> <upgrade fromrevision="5" cmd="..."/><BR>> <upgrade fromrevisiongreaterorequalthan="6" fromrevisionlessorequalthan="8"<BR>> cmd="..."/><BR>> <upgrade fromrevisiongreaterthan="8" cmd="..."/><BR>> <BR>> What do you think about this?<BR>
<BR>
I can see the point but it would become a very very lengthy xml file over the lifespan of a package such as Flash, Shockwave, Quicktime etc...<BR>
<BR>
Perhaps perform the upgrade first ONLY if the current XML file revision is greater than that currently installed on the computer?<BR>
<BR>
Chris<BR> <br /><hr />Chat to your friends for free on selected mobiles. <a href='http://clk.atdmt.com/UKM/go/174426567/direct/01/' target='_new'>Learn more.</a></body>
</html>