From owner-cvs-all Sat Oct 10 02:33:00 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12985 for cvs-all-outgoing; Sat, 10 Oct 1998 02:33:00 -0700 (PDT) (envelope-from owner-cvs-all) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12977; Sat, 10 Oct 1998 02:32:58 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: from dragon.nuxi.com (WHAT_THE_HELL_YOU_LOOKING_AT_@d60-147.leach.ucdavis.edu [169.237.60.147]) by relay.nuxi.com (8.8.8/8.6.12) with ESMTP id CAA17807; Sat, 10 Oct 1998 02:32:49 -0700 (PDT) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.1/8.9.1) id JAA23234; Sat, 10 Oct 1998 09:32:49 GMT (envelope-from obrien) Message-ID: <19981010023248.A23191@nuxi.com> Date: Sat, 10 Oct 1998 02:32:48 -0700 From: "David O'Brien" To: Satoshi Asami , wollman@khavrinen.lcs.mit.edu Cc: mark@grondar.za, committers@FreeBSD.ORG Subject: Re: Ports-with-crypto; a prpopsal Reply-To: obrien@NUXI.com References: <199810091934.PAA24399@khavrinen.lcs.mit.edu> <199810092249.PAA11783@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199810092249.PAA11783@silvia.hip.berkeley.edu>; from Satoshi Asami on Fri, Oct 09, 1998 at 03:49:46PM -0700 X-Operating-System: FreeBSD 3.0-BETA Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-cvs-all@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Garrett said everything I would have said -- so Mark, do you want to > start a repository of crypto distfiles and packages? Why do we need to do that? I think it was begining with 2.2.6, you didn't mind me gettting the crypto distfiles put on CDROM, but you didn't want to build packages for the release since packaging has never been tested. Since we are willing to produce CDROMs w/crypto why do we need to move the handeling of Crypto ports elsewhere? I don't remember our policy WRT wcarchive, so maybe placeing packages on markm's box might be good. Why not add building of Crypto files to your list of things you build, but put the package files elsewhere, where markm could mirror them. Keeping the handleing crypto ports the same as the rest of the ports is good for consistancy. > One thing we can do to make your life easier is to standardize the > variables. For instance, make bsd.port.mk rules to build only > packages when the variable RESTRICTED is set to the string "Crypto". I proposed a long time ago, that we add a new categrory "IS_CRYPTO" analagious to BATCH/INTERACTIVE/etc... At the time I don't think you wanted to add another varable. How about now? (I've dreamed of being able to build a set of crypto packages for the CDROM for quite some time) I think RESTRICTED should still stay freeform -- some people state what part/section/under what conditions, etc. the crypto restriction applies. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org)