PSM 2.0 is along to the point where we'd like other developers to start using to report bugs and what not. I'll be attaching a patch that will allow developers to build PSM 2.0 instead of PSM 1.x if developers choose to do so.
This patch causes everyone to pull mozilla/security/nss, NSS_3_2_RTM mozilla/security/manager, even when not building PSM 2.0. Is that intended?
is there any carbon work that needs to be done for the code to be turned on?
The new patch keeps the NSS version the same. I don't know how to make the Mac build system selectively check out, so I always check out PSM 1.x (mozilla/security/psm) and PSM 2.0 (mozilla/security/manager) If there is a way to selectively check out on the Mac, please let me know and I'll make this patch do that.
I don't think there is any carbon work that needs to be done. In talking to Patrick Beard, he told me not to add any dependencies on OS specific API's and to link against the stub libraries and that I'd be OK. AFAIK, I've done that, but please feel free to double check the project files.
No, you can't make the build system selectively check out based on an option flag right now, easily.
Fix checked in
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
changing QA contact to jj for verification.
QA Contact: granrose → jj
You need to log in before you can comment on or make changes to this bug.