On Mon, Feb 21, 2005 at 08:54:48AM +0100, Piotr Wadas wrote: > Date: Mon, 21 Feb 2005 08:54:48 +0100 (CET) > From: Piotr Wadas <[EMAIL PROTECTED]> > To: [email protected] > Reply-To: [email protected] > Subject: Re: [OpenCA-Devel] is CVS version buildable? > > > I've already pulled openca_0_9_2_1 from cvs and build packages, but > >have some errors and haven't figured out what to do next. > >1st of all, configure_etc didn't create openca_start and openca_stop, so > >I've just renamed templates to start/stop. > If anyone has any packages, I'm first to test it :) I tried to build some > debian packages, but unfortunately I wasn't succeeded - I'm not sure > whether there are any debian policy suggestions about openca, and what > are scheme of packages in ancient versions - e.g. I don't know whether > there was scheme like openca-[component]*deb, or Here's diff for 0.9.2.1 obtained with buildpackage, based on debian version by Alessandro Razeto from CVS. It builds packages on my Sarge system, but lintian gives some warnings which could be ignored for now. Perhaps we should ask Alessandro to update CVS after we fix lintian's warnings
> openca-ca*deb/openca-ext*deb. I guess in the first case there should be
> another packages for node interface for each component. However with
> scheme ca/ext packages there probably should be node component for ca in
> ca package, and configurable node component in ext package, depending
> which modules user will enable in config.xml.
it creates openca-{ca,ra,pub,node,doc} debians package.
> In a fact, what is general suggestion for using node interface ? If I plan
> my PKI with each component (ca/ra/pub/ldap..) on separate machine, it's
> clear
> that I should install node for each component with this component, but
> if I plan my PKI with ca on one machine and ra/pub/ldap on another
> (probably most common scheme) should I install node for ra/pub/ldap
> separately, or am I able to use the same installed node component for all
each of openca-{ca,ra,pub} packages depends on openca-node, so if you
install ra and pub packages there will be one node package.
> of them? Documentation isn't clear about it, however make install-ext
> installs one node interface for all. There's also some information about
> test installation with all components including ca on one machine in
> config.xml (yes, security, yes :), but I have no idea what about node
> interface in this case.
> BTW is there available some clear list what perl modules I need for
> OpenCA? I know that I'm able to use some modules installed with os (I also
> know about these debian modules versions issues), and use some (or all)
> included with openca tgz, but I think that list of all modules with
> suggested version and status (optional/obligatory/dependent by) would
Debianized packages already includes all necessary dependencies and
recommends libdbd-pg-perl | libdbd-mysql-perl, but _BEWARE_ of
libnet-server-perl package of 0.87-2 version. It doesn't accept
user/group like www-data. It supposed to be fixed in 0.87-1 bug
#223383, but is not.
here's link to diff for fixing it:
http://bugs.debian.org/cgi-bin/bugreport.cgi/new_server.diff?bug=223383&msg=6&att=1&archive=yes
> be useful. Such list would probably give me clear look which of the needed
> modules are available with debs, and which are distributed by openca or
> CPAN archives.
> To be frank with creating debian packages for openca, it would probably
> make sense to create packages for OpenCA::* modules, to make them
> available like other packaged perl modules - including them silently in
> openca*deb would be easier, but would probably cause some chaos.
Greetings
--
Alexei Chetroi
openca_0.9.2.1-1.diff.gz
Description: Binary data
