Hi again, +-------------- David [20030402 @ 20:08] -------------- | As far as I have understood from previous discussions and information | passed on the irc channel there wont be much support for prebinding | from our side in the near future.
I see. Thanks for the heads-up. Please do not get this wrong - by no means do I want to question your decisions. But I'm interested to hear why you want to keep prebinding disabled. I have experienced a quite noticable improvement in application startup time after prebinding the libraries used by that application, and I wasn't aware that prebinding can cause problems? | Mainly because we would have to find | a way how to distribute the address ranges that are used for prebinding | between the different projects. What is Apple's recommendation for preferred address selection? As far as I understand, the only challenge is to find an address range that is not also used by other libraries that the library directly links against... -- it does not have to be a system-wide unique address - since update_prebinding will take care of going through the dependencies and make sure that there are no overlaps later. Or am I wrong? That's at least how it appears from the update_prebinding manpage: update_prebinding tries to synchronize prebinding information for libraries and executables [...] a newly installed library or executable's pre-binding information might not match the libraries already on the disk [...] update_prebinding ensures that prebinding information is up-to-date after new prebound applications or new versions of system libraries are installed. | we have also determined that prebinding | can, in some rare cases, be detrimental to the package. Under what circumstances? Best regards, =/~ K -- Karin Kosina (vka kyrah) Systems in Motion
pgp00000.pgp
Description: PGP signature
