Jeff
The idea of a command line option to produce XPI files that are acceptable to the current mozilla browsers is one that could become an acceptable contribution to mozilla. I *encourage* you to pursue this until your contribution is accepted. Fame! Glory! :)
The best and right way to do that, IMO, is to register with bugzilla, then create a bugzilla "bug" (enhancement request) about this, and attach your source diffs to that bug as an attachment in bugzilla. newsgroup postings get lost and forgotten. Bugzilla bugs keep showing up in queries until they're fixed. :) If you're interested in that, I can provide you with a number of tips on how to make that go smoothely. Feel free to write me (you can demangle my email address above).
I believe that your patch should be coded to have the effect then when the new -X option is NOT supplied, the output of the tool is the same as version 1.3 produced before; files get output in the same order, values computed in the same way, same error messages for missing or unwritable directories, etc. The behavior should only change when the -X option is present.
So, now I have some questions about your new version of the code:
a) when the -X option is absent, does the program produce XPI files with the same content in the same order as version 1.3 did?
b) when the META-INF directory is unwritable, or doesn't exist and the parent directory is unwritable, and -X is absent, does the new tool produce the same graceful error messages as version 1.3?
c) same as question b, except -X is present.
If the answer to any of those questions is no, then please take another pass on the patch. Thanks.
/Nelson _______________________________________________ mozilla-crypto mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-crypto
