> Are there any plans to add support for component versioning to XPCOM in
> before this freeze?
none on the table. I would like to have some notion of a version per
component, but I guess that is what the CID and contract IDs are all
about.
> Once we freeze XPCOM, can we start versioning the shared library as well?
I hope so. I have a xpcom libray install in /usr/lib. I have clue what
version it is. I have seen makefile hacks to determine what version it
might be. Unacceptable. Maybe you can weigh in here. How hard would
it be to add versioning in an xp way?
> Are there any plans for creating a separate lib for the "non-core" parts
> of XPCOM? I vaguely recall another thread on this long ago but I can't
> seem to find it.
Yes, there is plenty of talk about moving many of the helper functions
like, nsCOMPtr, get_Service, and the string class into a static libary
that both xpcom and third partys can link to. This would all the third
party to no have to link to xpcom and therefore be independant. What do
you think?
