Kris Kennaway [EMAIL PROTECTED] writes:
On Mon, Jul 30, 2001 at 07:44:33AM -0700, David O'Brien wrote:
On Sun, Jul 29, 2001, Kris Kennaway wrote:
installed. This would involve a repo copy of crypto/openssl/crypto/bn
to contrib/openssl-bn or something, and I'd keep the two in sync
On Mon, Jul 30, 2001 at 07:44:33AM -0700, David O'Brien wrote:
On Sun, Jul 29, 2001, Kris Kennaway wrote:
installed. This would involve a repo copy of crypto/openssl/crypto/bn
to contrib/openssl-bn or something, and I'd keep the two in sync with
future vendor imports.
You're likely
On Sun, Jul 29, 2001, Kris Kennaway wrote:
installed. This would involve a repo copy of crypto/openssl/crypto/bn
to contrib/openssl-bn or something, and I'd keep the two in sync with
future vendor imports.
You're likely to get people saying repo bloat. And it does seem a
little wrong to
On Sun, Jul 29, 2001 at 02:06:58AM -0700, Dima Dorfman wrote:
I've imported the libmp-in-terms-of-OpenSSL library and connected it
to the build. I've also disconnected libgmp and friends from the
build, but have not `cvs rm`'d it yet. Assuming no problems turn up,
I plan to do that in two
Kris Kennaway [EMAIL PROTECTED] writes:
On Sun, Jul 29, 2001 at 02:06:58AM -0700, Dima Dorfman wrote:
I've imported the libmp-in-terms-of-OpenSSL library and connected it
to the build. I've also disconnected libgmp and friends from the
build, but have not `cvs rm`'d it yet. Assuming no
I think I might have missed part of this thread so forgive me
if this has already been brought up. We need to get a couple
of package builds under our belts before this gets MFCd. I
seem to recall there were a couple of ports that expected libgmp
to be around. If so, we'll need to weed those
On Sun, Jul 29, 2001 at 06:38:36PM -0500, Steve Price wrote:
I think I might have missed part of this thread so forgive me
if this has already been brought up. We need to get a couple
of package builds under our belts before this gets MFCd. I
seem to recall there were a couple of ports that
