Date: Thu, 5 Jun 2003 15:09:03 +0300 From: Ruslan Ermilov <ru@freebsd.org> To: Mark Murray <mark@grondar.org> Cc: arch@freebsd.org Subject: Re: A proposed drastic cleanup of the telnet build. Message-ID: <20030605120903.GB53363@sunbay.com> In-Reply-To: <200306051140.h55BeFHh013268@grimreaper.grondar.org> References: <20030605104620.GA47983@sunbay.com> <200306051140.h55BeFHh013268@grimreaper.grondar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--PmA2V3Z32TCmWXqI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 05, 2003 at 12:40:15PM +0100, Mark Murray wrote: [...] > > I'm not so sure about this. If it would be possible to extract > > the crypto bits of the telnet sources to separate source files, > > and leave them under src/crypto/, I think that would be the best, > > but if it's too hard, well, the price could be paid. >=20 > The point is that src/crypto is the part of the tree that will be > trimmed if there is a ban on crypto source. Part of the same point > is to avoid having duplicate sources, resulting in folks editing > only one and having code divergence between the two. >=20 I understand this. I just thought that it maybe possible to extract the crypto bits out of sources into separate =2Ec and .h files, so that we need to compile them together with non-crypto *.[ch] if we need crypto telnet. I now see that this is nearly impossible; the crypto bits are scattered all around the sources. But I have another important question here: Are the telnet sources really considered crypto sources? Yes, they use crypto functionality if compiled with the corresponding options, but they just USE them, they don't PROVIDE them. As such, should we treat them as restricted? If yes, I'd like to (please) hear why are they treated as such? If not, then the solution is obvious, keep them under src/*/(lib)telnet(d). Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software Ltd, ru@FreeBSD.org FreeBSD committer --PmA2V3Z32TCmWXqI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+3zLfUkv4P6juNwoRAo+GAJ9J2Pbib20Q+Tux5ketZKaiTvfbJQCffO5V /WVfkybgu3CbDa7MP+awoMk= =/SAz -----END PGP SIGNATURE----- --PmA2V3Z32TCmWXqI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030605120903.GB53363>