From owner-freebsd-current Sat Feb 19 14:37:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id CC08337BD26; Sat, 19 Feb 2000 14:37:14 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA41347; Sat, 19 Feb 2000 14:37:08 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-reply-to: Your message of "Sat, 19 Feb 2000 13:53:51 PST." Date: Sat, 19 Feb 2000 14:37:08 -0800 Message-ID: <41344.950999828@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > openssl becomes a "distribution" like the DES bits are. Depending on > > external packages is actually something I'm trying to wean sysinstall > > away from because the dependency is a PITA and the creation of the > > packages collection is not automated in the same way that distribution > > building is. > > Okay, so what do I need to do to make this happen? 1. Make openssl build as part of the standard "world" and depend on the setting of USA_RESIDENT, which will be initially set by sysinstall. 2. Let me look at where things are installed in each case (if there's any difference at all) and figure out how to hack release/Makefile to package up the extra bits. 3. I add another "crypto" flag for this chunk of stuff in the now-not-very-well-named des/ distribution directory and add sysinstall menu entries for it appropriately. Of course, this all begs the question as to whether or not the current DES/openssl division is even meaningful now. The DES code we have in the tree is rapidly falling under the radar of what the US government considers interesting and this whole openssl thing is over a patent, which is in a rather different category. We're sort of trying to skate in-between the lines here and I think we're only confusing ourselves as a result. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message