10 messages in org.freebsd.freebsd-stableRe: 4.1-RELEASE will be tagged and do...| From | Sent On | Attachments |
|---|---|---|
| John Baldwin | Jul 25, 2000 12:25 pm | |
| John Baldwin | Jul 25, 2000 3:30 pm | |
| Kris Kennaway | Jul 25, 2000 4:27 pm | |
| Jordan K. Hubbard | Jul 26, 2000 12:41 am | |
| Kris Kennaway | Jul 26, 2000 1:29 am | |
| John Polstra | Jul 26, 2000 9:04 am | |
| Dwight Tuinstra | Jul 26, 2000 9:31 am | |
| Brandon D. Valentine | Jul 26, 2000 12:16 pm | |
| Kris Kennaway | Jul 26, 2000 3:43 pm | |
| Kris Kennaway | Jul 27, 2000 4:59 am |
| Subject: | Re: 4.1-RELEASE will be tagged and done tonite, starting at 18:00 PDTT | |
|---|---|---|
| From: | Brandon D. Valentine (ban...@looksharp.net) | |
| Date: | Jul 26, 2000 12:16:26 pm | |
| List: | org.freebsd.freebsd-stable | |
On Wed, 26 Jul 2000, John Polstra wrote:
I would lean more toward keeping the crypto code in separate distributions for a while longer. When we folded the cvs-crypto CVSup collection into cvs-all, I got an e-mail from one person who was quite upset because he assumed it meant that crypto wouldn't be in separate binary distributions any more. At least to him, it was important to keep the ability to be completely crypto-free.
It's no longer possible to be crypto free if you're a -current user. Make of that what you will.
As for changing the crypto distributions, I would recommend holding off until the RSA patent expires before making any more changes in the crypto structure. At that time we will have to alter our current crypto mechanisms anyway so it makes much more sense to do it all at once. It's a lot easier if you can issue a HEADS UP warning people not to update during a given window and then make all of your crypto related repository changes at once, following up with instructions on how to use the new crypto collections and the official notice to begin updating again.
Brandon D. Valentine
-- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying
To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message