Hi,

> I did not try this to build a "default" OpenCA. Why are there a
> workaround in  the first place?

The workaround is present because we have components which must be
installed in exec_prefix. Autoconf doesn't resolve ${exec_prefix} if it is
not explicitly set by --exec-prefix. Therefore we constructed a simple
workaround which resolves the variable. EXEC_PREFIX is this workaround.

> I use this patch to never touch any of the modules:
>
> --- src/Makefile        2004-04-19 13:08:25.167875312 +0200
> +++ src/Makefile.oden   2004-04-19 13:13:47.415886168 +0200
> @@ -15,7 +15,6 @@
>
>  SUBDIRS = \
>         $(COMMON_DIR)   \
> -       $(MODULE_DIR)   \
>         $(OPENCA_SV)    \
>         $(SCRIPT_DIR)   \
>         $(WEB_DIR)      \
>
> IMHO the whole src/modules directory should be removed from the OpenCA
> tar  ball. The software suite should be as modular as possible. If
> there's a  problem with for example the "OpenCA-Tools" perl module, one
> could easily  just update that specific package (thinking RPM packages
> here...).

Ok, perhaps I should better document what I'm doing for SuSE. Until now I
don't understand how you create all the packages with one spec file but I
know how to disable the module installation :)

If you configure OpenCA with --enable-package-build then no common parts
will be automatically installed - this includes the modules. Please take a
look in our suse directory in the CVS. We compile seperate RPMs for every
Perl module. make install-common only installs components from src/common/
but not from src/modules.

Does it be possible to see the configure and spec files somewhere on the
web. This would ease the analysis.

Best regards Michael





-------------------------------------------------------
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

Reply via email to