remove misleading comment in spec file concerning jar signing
This commit is contained in:
parent
8ea99e33ee
commit
822fd75c16
18
jss.spec
18
jss.spec
@ -1,6 +1,6 @@
|
||||
Name: jss
|
||||
Version: 4.2.6
|
||||
Release: 12%{?dist}
|
||||
Release: 13%{?dist}
|
||||
Summary: Java Security Services (JSS)
|
||||
|
||||
Group: System Environment/Libraries
|
||||
@ -121,19 +121,6 @@ ln -fs %{_libdir}/jss/jss4.jar $RPM_BUILD_ROOT%{_jnidir}/jss4.jar
|
||||
install -d -m 0755 $RPM_BUILD_ROOT%{_libdir}/jss
|
||||
install -m 0755 mozilla/dist/Linux*.OBJ/lib/libjss4.so ${RPM_BUILD_ROOT}%{_libdir}/jss/
|
||||
|
||||
# FIXME - sign jss4.jar. In order to use JSS as a JCE provider it needs to be
|
||||
# signed with a Sun-issued certificate. Since we would need to make this
|
||||
# certificate and private key public to provide reproducability in the rpm
|
||||
# building we have to ship an unsigned jar.
|
||||
#
|
||||
# Instructions for getting a signing cert can be found here:
|
||||
# http://java.sun.com/javase/6/docs/technotes/guides/security/crypto/HowToImplAProvider.html#Step61
|
||||
#
|
||||
# This signing is not required by every JVM. gcj ignores the signature and does
|
||||
# not require one. The Sun and IBM JVMs both check and enforce the signature.
|
||||
# Behavior of other JVMs is not known but they probably enforce the signature
|
||||
# as well.
|
||||
|
||||
# javadoc
|
||||
install -d -m 0755 $RPM_BUILD_ROOT%{_javadocdir}/%{name}-%{version}
|
||||
cp -rp mozilla/dist/jssdoc/* $RPM_BUILD_ROOT%{_javadocdir}/%{name}-%{version}
|
||||
@ -155,6 +142,9 @@ rm -rf $RPM_BUILD_ROOT
|
||||
|
||||
|
||||
%changelog
|
||||
* Mon Jan 31 2011 John Dennis <jdennis@redhat.com> - 4.2.6-13
|
||||
- remove misleading comment in spec file concerning jar signing
|
||||
|
||||
* Tue Jan 11 2011 Kevin Wright <kwright@redhat.com> - 4.2.6-12
|
||||
- added missing patch line
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user