On 6/19/11 7:53 PM, Justin Wood (Callek) wrote: > On 6/19/2011 10:13 PM, David E. Ross wrote: >> On 6/19/11 6:04 PM, Steve Wendt wrote: >>> On 06/19/11 04:50 pm, David E. Ross wrote: >>> >>>>> Preserve Download Modification Timestamp >>>>> <https://addons.mozilla.org/addon/preserve-download-modification> is >>>>> compatible with SeaMonkey 2.1. >>>> >>>> That extension is compatible only if you tweak the maxVersion in file >>>> install.rdf. >>> >>> ??? Works with: SeaMonkey 2.0 - 2.4a1 >> >> That's what the Web page says. However, the install.rdf file has >> <em:maxVersion>2.1b3</em:maxVersion> >> for SeaMonkey. >> > > Which is because if you already had installed it it doesn't modify the > local HD file, but any check for updates on AMO will mark it compat for > SeaMonkey. > > Also any fresh download from AMO will correct it. > > AMO allows developers to mark an addon as compat on their dev interface > and AMO does that magic itself, keeping users from having to download a > whole file on each "compat tweak" rather than actual code change. >
I did a fresh download just before posting my reply. I expanded the XPI file (which is actually a zip file) with WinZip and viewed the install.rdf file with WordPad. Are you saying that somewhere there is something that tells the Add-ons Manager to ignore maxVersion in install.rdf? -- David E. Ross <http://www.rossde.com/> On occasion, I might filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam from that source. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
