Waiting for the next release of Mozilla Update
I was trying to update the Launchy entry at Mozilla Update but I kind of gave up. Getting these very unuserfriendly error messages:
Error! The MaxAppVer for Firefox of 1.1 in install.rdf is invalid.
Error! The MinAppVer for Netscape of 0.1 in install.rdf is invalid.
Error! The MinAppVer for Nvu of 0.1 in install.rdf is invalid.
Error! The MaxAppVer for Nvu of 1.0 in install.rdf is invalid.
Why cant it at least tell what the valid choices are? Damn programmers! When will there be a new and better release of Mozilla Update?
Ads:
10 Comments
1.1 isn't a good choice, 1.0+ is. 1.1 is for final, and stuff might/will break between now and then....
Comment by Mike at May 30, 2005 11:21 PM | PermalinkI think the issue here is that UMO should ignore any 'invalid' entries and still allow you to submit the extension with only the 'valid' entries available.
Comment by Jed at May 30, 2005 11:29 PM | Permalinkmconnor is right. Jed is wrong. At least for now. That may change. The problem is that everything on UMO gets tested and we restrict the install.rdf to released versions. Deer Park is 1.0+, not 1.1. We can't just ignore invalid entries because (1) someone would want to know why it didn't get parsed and (2) Firefox itself would still allow it to come in.
Comment by alanjstr at May 31, 2005 01:09 AM | PermalinkGiving this entry the title "Waiting for the next release of Mozilla Update" and ending it with "When will there be a new and better release of Mozilla Update?" makes it sounds like you're demanding and expecting that your issue be fixed before even telling the UMO developers what the issue is.
Comment by Jesse Ruderman at May 31, 2005 02:38 AM | PermalinkJesse: What are the valid choices for Netscape or for Nvu?
Comment by Henrik Gemal at May 31, 2005 10:03 AM | PermalinkThe valid choices for Netscape (3db10fab-e461-4c80-8b97-957ad5f8ea47) seems to be:
<em:minVersion>8.0</em:minVersion>
<em:maxVersion>8.0.1</em:maxVersion>
> What are the valid choices for [...] or for Nvu?
Hopefully none as app.extensions.version was always 1.0 and there are major rewrites in progress.
A better question to ask is when will there be something final in the open source community? I've long been a open source enthusiast of open source software but crashes like this is just plain annoying. When will the FOSS community mature? And please spare me the usual rant about the continuous development of ideas and software. Hint: make something stable, release an alpha/beta/final, repeat as needed. Note that this is not like the Microsoft development cycle which is develop/release/patch.
Comment by Anders Raben Hansen at June 2, 2005 11:23 PM | PermalinkWhat are valid choices for SeaMonkey (or Mozilla Suite)????
Comment by Alfred Kayser at August 30, 2005 08:46 PM | Permalink
Using "1.1" as the MaxAppVer doesnt work for some weird reason, I suspect it will once the official final release comes rolling out. For now, to have it work on Deer Park/ Nightly Trunk builds, make the MaxAppVer "1.0+". I know it works, because I modified Launchy's install.rdf file on my own to achieve finctionality on Nightly trunk builds.
Comment by Dan DeVaney at May 30, 2005 11:18 PM | PermalinkLatas!