To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=88700


User jl changed the following:

                What    |Old value                 |New value
================================================================================
                 Summary|to-be-BEA300_m1/DEV300_m11|to-be-BEA300_m1: extension
                        |: extensions and arch in I|s and arch in Identifier:
                        |dentifier:                |
--------------------------------------------------------------------------------




------- Additional comments from [EMAIL PROTECTED] Fri Apr 25 12:26:25 +0000 
2008 -------
>Now we have "the identifier MUST be unique. This is also the case when two
>extensions are logically the same but support different platforms." so is this
>indicating that an extension built from the same source for different archs has
>a different identifier (as in the identifier used to manipulate it with unopkg)
on each arch ? 
Yes.
The platforms that an extension supports are in that platform tag
and we know our own platform, isn't that all that's required to figure out
what's suitable to upgrade to ?
Yes. See issue 87803.

I am preparing cws jl99 on which i will adjust the Extension Manager to use the
platform strings case insensitive. And the pdf import can than be fixed on this
cws as well as other extensions which have the same problem.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to