On 01-03-27 14:48:56 MET DST, Michael Bell wrote:
> it's nice to have such an active tester. Could you check in the bugs
> which you find into the bugtracking system on sourceforge please? We
> have serious problems to track all the bugs which are posted via
> mailings lists. Therefore we start moving to sourceforge.
>
> You can enter the bugs without having an account on sourceforge
> (http://sourceforge.net/projects/openca/).
i even got myself an account last week, i case you decide that you want
me as a developer. :-)
no, i'm serious. perhaps in a few weeks.
of course i can file a bug report in your newly furnished sourceforge
home and attach a patch where i bend your hardwired paths into my
hardwired paths, but i'd rather prefer providing a better solution to
the project, i.e. change the stuff so that it puts the right paths into
the files upon installation.
but i'm not sure what exactly to suggest.
i'm not very happy with your linux-specific scripts (calling /bin/bash,
which has yet to become standard on unix OSes) and your interactive
makefiles.
what do you think about converting to autoconf and letting it do the
substitutions?
well, openca contains a collection of perl modules, too, where perl'ing
Makefile.PL is the standard way to configure... i'm not sure whether
and how both should be combined, or whether everything should be done
via MakeMaker.
(currently, you are even using autoconf for a perl module (OpenCA-SV).)
anyway, i'll make a new diff, against the 010326 snap, and file it in
the bug system.
rj
_______________________________________________
OpenCA-Devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/openca-devel
