Hi Stephan,
I'll try to answer too :)
Point 1 : libsalsystools.dylib
For both aqua and X11 versions, in aquavcl01 cws, I have removed
libsalsystools, because current dir was not found, and a lot of random
bugs were fixed this way ( locale not detected is never good :) )
Result is : on Mac OS X, the locale detection is now included in
libuno_sal.dylib, and your changes are not needed anymore, if you agree
them, of course ( simplify locale detection). See module.c and
nlsupport.c + osxlocale.cxx for more infos.
To complete : aquavcl01 is in integration process, and a cws-clone of
sal + scp2 changes , called salaquatox11 has been created, (you are
welcome to have a look and give your opinion ). Once salaquatox11
integrated, all aquavcl01 changes in sal + scp2 will disappear.
FYI, Oliver will do deep changes on Mac OS X port, in sal, but only once
aquavcl01 is integrated : our objectives are firstly to not break other
architectures, and secondly improve aqua port (we know osxlocale needs
some rework )
Point 2 : Baseline
It was announced sometimes ago, and this is still true :
=> *10.4 is our official baseline* ( Aqua is not 10.3 compatible )
Point 3 : Panther (i.e. 10.3 compatibility )
The current distribution between Intel and PowerPC machines is
approximatively 70% Intel vs 30% PowerPC
If ever 50% of PowerPC users does use Panther, it means there are *sure*
less than 20% of Mac users using PowerPC machines and running Panther.
=> Panther will be at its end of life at the end of the year.
*But*, an important park of machines using OpenOffice.org continues to
use 10.3 (I know some administrations), and I'd suggest to :
- avoid incompatible changes until Leopard output, say somewhere in
October 2007 (better : end 2007 )
- start with patch including Panther cases, until Aqua version is
stable, or close to be ( early 2008 probably)
Waiting, and if ever this is possible, we will try to maintain Panther
build : I myself contributed with macosxpbuildrepair some times ago),
and Maho did a few days ago.
Panther will soon become unmaintainable, but it is sensible and
important to continue to provide *as long as possible* Panther
compatibility for PowerPC builds.
Point 4 : @loader_path
Yes, use it is suggested by Apple, this is a good idea (e.g. this
enables the construction of bundles and other "directory trees" of final
linked images which can be installed anywhere). libsalsystools.dylib was
not the only one concerned and there is probably some work to do.
Just : can we postpone a bit the changes you scheduled ?
Regards,
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
