To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=88700
                 Issue #|88700
                 Summary|to-be-BEA300_m1: extensions and arch in Identifier:
               Component|framework
                 Version|current
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P1
            Subcomponent|code
             Assigned to|mba
             Reported by|rene





------- Additional comments from [EMAIL PROTECTED] Thu Apr 24 15:43:53 +0000 
2008 -------
[ Cc'ing the active porters, pl and jl because they apparently talked about this
 and ause ]

Hi,

I just saw
http://www.go-ooo.org/bonsai/cvsview2.cgi?command=DIFF&subdir=framework%2Ffilter%2Fsource%2Fpdfimport%2Fconfig&file=description.xml&rev1=1.2&rev2=1.2.10.1&whitespace_mode=show&diff_mode=context
and
http://www.go-ooo.org/bonsai/cvsview2.cgi?command=DIFF&subdir=framework%2Ffilter%2Fsource%2Fpdfimport&file=pdfisettings.pmk&rev1=1.3&rev2=1.3.6.1&whitespace_mode=show&diff_mode=context.
when looking at cws pdfimportfix which got cloned and integrated for BEA300_m1 [
and pl tells me that the cws presenterscreen will change it in the same way for
the Presenter Screen ]

pl explains me on IRC that it should be needed in the Identifier (which I doubt,
it worked so far, too, and you can addd the arch(s) in jls new extension field
instead of the *Identifier*) but the more severe problem is that it causes a
burden for anyone not building on a "Sun-arch".

The Identifier contains $(PLATFORMID) which is then substituted by the one set
in settings.mk. This only only contains the Sun-archs, though.
What are you going to do on the other archs?
  a) Add every arch there from scratch?
  b) revert the whole thing and use a unique identifier?

If you choose a) you'd need to add every arch (note that OOo does support more
archs than only x86: x86_64, s390, sparc, ia64, ppc, ppc64, mips, arm) there.
This code is set in every module, though, so it should be moved somewhere to
solenv if we do that.

Note that this is also a maintainance burden, since for bundled extensions you
need to know the Identifier in advance so you can remove it via unopkg, and you
have to have different scripts depending on the arch there....

If you choose b) the whole thing is solved immediately.

Otherwise you get broken extension Indentifiers à la: "foo.bar,baz-" instead of
"foo.bar.baz-Linux_x86".

---------------------------------------------------------------------
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