From af5e13c7bdadb11a17d37ee8b71f6dd077ac0304 Mon Sep 17 00:00:00 2001 From: "http://petefoth.myopenid.com/" Date: Mon, 14 Nov 2011 07:10:01 -0500 Subject: [PATCH] --- design/librarymacinstallerplan.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/design/librarymacinstallerplan.mdwn b/design/librarymacinstallerplan.mdwn index d15b94d..022811e 100644 --- a/design/librarymacinstallerplan.mdwn +++ b/design/librarymacinstallerplan.mdwn @@ -28,7 +28,7 @@ Secondary goals are ###Issues and questions ####To be resolved ASAP Q: Luke> What's the actual framework binary (that is, /Library/Frameworks/Moonshot.framework/Moonshot) going to link to -- libmoonshot-ui? That would make the most sense as mech_eap and the GS2 SASL plugin aren't directly linked against by applications. By convention, you'll need to have something there (otherwise it's not really a framework). -> A: Pete> I was planning to link /Moonshot.framework/Moonshot to the mech_eap dynamic library. libmoonshot-ui (or whatever replaces it in the refactored Identity Selector software) will be created and installed when we port the Identity Selector to Mac OS, which is a separate task. As I understand it, mech_eap *is* the Moonshot GSS EAP library. If it isn't directly linked against by applications, do we just install it in /usr/local/lib and forget about creating a framework. I still need to get to the bottom of this issue, before I start making the installer for it. +> A: Pete> I was planning to link /Moonshot.framework/Moonshot to the mech_eap dynamic library. libmoonshot-ui (or whatever replaces it in the refactored Identity Selector software) will be created and installed when we port the Identity Selector to Mac OS, which is a separate task. As I understand it, mech_eap *is* the Moonshot GSS EAP library. If it isn't directly linked against by applications, do we just install it in /usr/local/lib and forget about creating a framework? I still need to get to the bottom of this issue, before I start making the installer for it. Q: Pete> New issue - do we need to do the versioning as suggested in the plan, or can we just overwrite the existing installation? ####To be resolved during implementation -- 2.1.4