Date: Sat, 10 Oct 1998 20:19:17 -0700 (PDT) From: asami@FreeBSD.ORG (Satoshi Asami) To: obrien@NUXI.com Cc: wollman@khavrinen.lcs.mit.edu, mark@grondar.za, committers@FreeBSD.ORG Subject: Re: Ports-with-crypto; a prpopsal Message-ID: <199810110319.UAA13461@bubble.didi.com> In-Reply-To: <19981010023248.A23191@nuxi.com> (obrien@NUXI.com)
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett has (again) answered to the gist of your questions. * 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. Yes, I think it's better to keep them all on Mark's box as the source for mirrors who can legally take them. * 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. I'd very much rather have someone else do it for me. ;) * 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 guess that's fine too. What should the logic for disabling/enabling be, btw? * P.S. am I going to get the crypto distfiles placed on CDROM for 3.0? Oh, yes, please. Thanks. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810110319.UAA13461>