Nicolas Mailhot wrote on 7/6/2004, 6:56 AM:
>
> If I can use the on-system mozilla nss
> installation all the nss security updates...
> are handled by the distribution provider.
>
> If I ship my own nss there will be sync
> problems, duplicated maintenance etc. This
> is especially true as jpackage targets a lot
> of different distributions so you can multiply
> this effort by 12 (a lot more hassle than a
> common source package people can rebuild
> easily on their system using their own nss
> version).
>
> Avoiding code duplication is a golden rule
> of Linux packaging.
If you are willing to patch the JSS sources
for your JSS Linux package, you can modify
some JSS makefiles to specify the locations
of NSPR and NSS headers and libraries.
For example, you can modify
mozilla/security/coreconf/headers.mk as
follows:
Index: headers.mk
===================================================================
RCS file: /cvsroot/mozilla/security/coreconf/headers.mk,v
retrieving revision 1.7
diff -u -r1.7 headers.mk
--- headers.mk 15 Feb 2002 22:53:13 -0000 1.7
+++ headers.mk 6 Jul 2004 18:09:40 -0000
@@ -57,4 +57,6 @@
INCLUDES += -I$(SOURCE_XP_DIR)/include $(MOZILLA_INCLUDES)
endif
+INCLUDES += -I$(NSPR_INCLUDE_DIR) -I$(NSS_INCLUDE_DIR)
+
MK_HEADERS = included
and modify
mozilla/security/jss/lib/config.mk as follows:
Index: config.mk
===================================================================
RCS file: /cvsroot/mozilla/security/jss/lib/config.mk,v
retrieving revision 1.18
diff -u -r1.18 config.mk
--- config.mk 17 Oct 2002 00:33:32 -0000 1.18
+++ config.mk 6 Jul 2004 18:21:24 -0000
@@ -68,6 +68,7 @@
else
EXTRA_SHARED_LIBS += \
+ -L$(NSPR_LIB_DIR) -L$(NSS_LIB_DIR) \
-L$(DIST)/lib \
-lnss3 \
-lsmime3 \
Then you just need to define the environment
variables NSPR_INCLUDE_DIR, NSPR_LIB_DIR,
NSS_INCLUDE_DIR, and NSS_LIB_DIR
appropriately before you build JSS.
Wan-Teh
_______________________________________________
mozilla-crypto mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-crypto
