If anyone has any packages, I'm first to test it :) I tried to build someI'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.
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 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.
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 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
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.
Regards, Piotr
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ OpenCA-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openca-devel
