Date: Wed, 25 Feb 2004 22:30:42 +0000 From: Colin Percival <colin.percival@wadham.ox.ac.uk> To: obrien@FreeBSD.org Cc: ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/security/freebsd-update Makefile Message-ID: <6.0.1.1.1.20040225220926.0401d1d8@imap.sfu.ca> In-Reply-To: <20040225190457.GA87595@dragon.nuxi.com> References: <6.0.1.1.1.20040225180234.03f7e008@imap.sfu.ca> <20040225190457.GA87595@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 19:04 25/02/2004, David O'Brien wrote: >What is going to break??? When I wrote the RSA code, I was thinking about one specific platform: i386. I made an attempt to be word-size / endian agnostic, but I'm not willing to guarantee that I didn't make any mistakes -- and I *know* that the code fails due to IEEE arithmetic problems on some Alpha systems. The fact that the code compiles on a particular platform is in no way a guarantee that it works properly. >When are you going to do this great analysis >you said needs to happen? I was planning on doing it after 5.2.1 was out of the way. If I had known that this was going to be an issue, I could have done the testing earlier, but I didn't think this was going to be a problem yet. Quite apart from that, the freebsd-update script fetches files from a URL which depends only upon the FreeBSD version number -- obviously, this needs to have `uname -p` added. All this is, however, irrelevant: I was listed as the MAINTAINER, and I explicitly stated that nobody should touch that port without approval. Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.1.1.1.20040225220926.0401d1d8>