[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [GNU Crypto] RFC: merging GNU Crypto and Jessie
From: |
Raif S. Naffah |
Subject: |
Re: [GNU Crypto] RFC: merging GNU Crypto and Jessie |
Date: |
Thu, 8 Dec 2005 05:41:14 +1100 |
User-agent: |
KMail/1.8.3 |
On Tuesday 06 December 2005 18:42, Casey Marshall wrote:
> A few of us have been throwing around the idea of merging GNU Crypto
> and Jessie into GNU Classpath, so Classpath will have full support
> for crypto and SSL "out of the box." We've proposed this before, and
> I think this idea was mostly approved by the group, but no-one ever
> got around to doing it.
>
> I'd like to propose again that we do this. I'll try to get to this
> myself, but if I can't get this done, we'll at least have a plan of
> action. I propose that we
>
> - Rename the root package 'gnu.crypto' to 'gnu.javax.crypto' in
> GNU Crypto, and merge the current CVS sources into Classpath (not
> under external/). We then put GNU Crypto into a kind of "stasis"
> mode, and continue to develop these sources in Classpath.
may i suggest the following alternative:
* tag the CVS with "2.2.0".
* release (a final) GNU Crypto 2.2.0.
* start moving gnu.crypto.* to Classpath
* test Classpath with new crypto classes.
* after Classpath 0.20 (or even may be 0.21) retire GNU Crypto.
> - Rename the root package 'org.metastatic.jessie' to
> 'gnu.javax.net.ssl' in Jessie, and merge the current sources. Then,
> I'll stop developing that branch on its own.
>
> We can then also merge other parts of GNU Crypto to projects where
> they make sense; its testsuite can go into Mauve (it was written to
> use (a possibly old version of) Mauve's own test harness classes),
> and the various tools can go into cp-tools.
>
> I think most Classpath hackers think this is a good idea; I'm sending
> this mail out to the individual project lists to see if there are any
> objections from users of either package. To be clear, GNU Crypto
> won't go away, while Jessie will. GNU Crypto MAY continue to be
> developed, but not by me (and if history is a precedent, then neither
> by anyone else).
>
> If I'm not able to put this patch together, I will answer anyone's
> questions about how to proceed, if we get a volunteer.
>
> Thanks.
cheers;
rsn
pgp5HiFoHFNaN.pgp
Description: PGP signature
Re: [GNU Crypto] RFC: merging GNU Crypto and Jessie, Raif S. Naffah, 2005/12/07
Re: [GNU Crypto] RFC: merging GNU Crypto and Jessie,
Raif S. Naffah <=
[GNU Crypto] Re: RFC: merging GNU Crypto and Jessie, Anthony Green, 2005/12/08
- [GNU Crypto] Re: RFC: merging GNU Crypto and Jessie, Casey Marshall, 2005/12/08
- [GNU Crypto] Re: [Jessie-discuss] Re: RFC: merging GNU Crypto and Jessie, Mark Wielaard, 2005/12/11
- [GNU Crypto] Re: [Jessie-discuss] Re: RFC: merging GNU Crypto and Jessie, Anthony Green, 2005/12/11
- [GNU Crypto] Re: [Jessie-discuss] Re: RFC: merging GNU Crypto and Jessie, Mark Wielaard, 2005/12/11
- [GNU Crypto] Re: [Jessie-discuss] Re: RFC: merging GNU Crypto and Jessie, Anthony Green, 2005/12/11
- [GNU Crypto] Re: [Jessie-discuss] Re: RFC: merging GNU Crypto and Jessie, Mark Wielaard, 2005/12/11
- [GNU Crypto] Re: [Jessie-discuss] Re: RFC: merging GNU Crypto and Jessie, Anthony Green, 2005/12/11
- Re: [GNU Crypto] Re: [Jessie-discuss] Re: RFC: merging GNU Crypto and Jessie, Raif S. Naffah, 2005/12/12
- Re: [GNU Crypto] Re: [Jessie-discuss] Re: RFC: merging GNU Crypto and Jessie, Anthony Green, 2005/12/12