torsdagen den 15 april 2004 15.19 skrev Michael Bell:
> > Yes I know now. Quite funny actually. The thing is that I got the
> > configure_etc.sh thing working yesterday, it turned out I had a
> > OpenCA-Tools v0.4.3 that did not work and differed from the one found
> > at the
> > ftp.cert.dfn.de ftp resource. What download resource is authorative,
> > accurate and up to date?
>
> We always ship the used modules together with an OpenCA snapshot, RC or
> release. The authorized source for the module is always "cd src/modules"
>
> :)
Ok, got it. Thank you. I used the source from your latest suse packages.
> Nevertheless it is possible to seperate the modules from the rest if you
> want to build packages. I don't know what you are doing. If you want to
> setup a working CA then please use the modules installed from src/modules.
> These modules are installed automatically. You can specify a special path
> where to install the OpenCA modules. ./configure
> --with-module-prefix=/usr/local/openca/ will install all the modules to
> /usr/local/openca/perl5. If you want to build packages please check
> OpenCA's CVS and then the suse area for an example :)
I used parts from your latest suse spec files from this url (thanks!):
ftp.cert.dfn.de/pub/pca/tools/openca/developers/bell/suse/8.2/openca_0_9_2_RC_3/
The main thing that differs from yours is that I use case sensitive naming of
the external perl modules like "perl-OpenCA-OpenSSL". Also I use spec file
magic and uses only one spec file (and one source tar ball) for producing all
the openca-* stuff. This is how:
INSTALL_STUFF="ca common ldap pub ra scep node"
for i in $INSTALL_STUFF; do
make \
DEST_BINDIR="%{buildroot}%{_bindir}" \
DEST_DATADIR="%{buildroot}%{_datadir}/openca" \
DEST_LIBDIR="%{buildroot}%{_libdir}" \
DEST_MANDIR="%{buildroot}%{_mandir}" \
DEST_SBINDIR="%{buildroot}%{_sbindir}" \
DEST_LIB_STYLESHEET_DIR="%{_datadir}/openca/stylesheets" \
DESTDIR="%{buildroot}/installed_stuff-${i}" \
install-${i}
done
for i in $INSTALL_STUFF; do
cp -rp %{buildroot}/installed_stuff-${i}/* %{buildroot}/
rm -rf %{buildroot}/installed_stuff-${i}
done
This makes these packages:
openca-common
openca-doc
openca-ocspd
openca-scep
openca-sv
openca-web-interfaces-ca
openca-web-interfaces-ldap
openca-web-interfaces-node
openca-web-interfaces-pub
openca-web-interfaces-ra
openca-web-interfaces-scep
One needs to be able to build packages as non root, so I use this before make
install:
On one single line:
find -name "Makefile*" | xargs perl -pi -e "s|-o \\\${httpd_user}||g;s|-g
\\\${httpd_group}||g;s|-o \\\${openca_user}||;s|-
g \\\${openca_group}||g"
Of course one needs to know the exact ownership (and file access rights) in
the %files section for each sub package.
Thanks Michael.
Cheers.
--
Regards // Oden Eriksson
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
OpenCA-Devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/openca-devel
