Date: Sat, 29 Jan 2000 22:41:25 +0200 From: Mark Murray <mark@grondar.za> To: "David E. O'Brien" <obrien@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/compat/compat3x Makefile libc.so.3.gz.uu libc_r.so.3.gz.uu libcurses.so.2.gz.uu libdialog.so.3.gz.uu libedit.so.2.gz.uu libf2c.so.2.gz.uu libftpio.so.4.gz.uu libg++.so.4.gz.uu libmytinfo.so.2.gz.uu libncurses.so.3.gz.uu ... Message-ID: <200001292041.e0TKfPw64330@gratis.grondar.za> In-Reply-To: <200001292021.MAA06551@freefall.freebsd.org> ; from "David E. O'Brien" <obrien@FreeBSD.org> "Sat, 29 Jan 2000 12:21:50 PST." References: <200001292021.MAA06551@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> obrien 2000/01/29 12:21:50 PST > > Removed files: > lib/compat/compat3x Makefile libc.so.3.gz.uu What happens if there are crypto files that need this treatment? In the post 4.0 world, I am aiming my bazooka at libdes in favour of libcrypto, and I can see a need for a compatability-mode libdes. This will (may?) need special treatment... M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org 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?200001292041.e0TKfPw64330>