On 01-08-23 16:46:07 CEST, Massimiliano Pala wrote:
> Michael Bell wrote:
>
> >
> > So what we should do:
> > * unzip OpenCA's modules
> > * remove the old tree openca/
> >
> > The directories openca-xyz I would not remove only no longer maintain
> > them because we could destruct needed code.
>
> So, If I can understand you, the proposed structure for the CVS would be:
>
> openca-0.9/
> [...]
> openca-0.9/src
> openca-0.9/src/modules/
> openca-0.9/src/modules/openca-x509
> openca-0.9/src/modules/openca-openssl
> openca-0.9/src/modules/openca-crl
> [...]
>
> and when the 1.0 will be under development:
>
> openca-1.0/
> [...]
> openca-1.0/src
> openca-1.0/src/modules/
> openca-1.0/src/modules/openca-x509
> openca-1.0/src/modules/openca-openssl
> openca-1.0/src/modules/openca-crl
> [...]
i agree with this layout, ...
> this would generate duplication of CVS code for the modules...
.. but i would use branches instead of directories, resulting in...
openca/
[...]
openca/src/
openca/src/modules/
openca/src/modules/openca-x509/
openca/src/modules/openca-openssl/
openca/src/modules/openca-crl/
[...]
on the directory level and cvs branches othogonal to them.
but i would accept michael's directory layout if mismaps with cvs
branches are to be expected.
> My point is that modules development is to be separated from the main
> project so we can still use the 'openca-xxx' for release development
> and drop the openca/ main cvs dir but I would continue to have
> modules cvs directories in the main cvs tree (and not in openca-xxx
> subdirs).
how are we gonna track which modules' versions fit which core-openca
versions?
rj
_______________________________________________
OpenCA-Devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/openca-devel
