From owner-freebsd-questions Sat Sep 2 17:12:47 2000 Delivered-To: freebsd-questions@freebsd.org Received: from inconnu.isu.edu (inconnu.isu.edu [134.50.8.55]) by hub.freebsd.org (Postfix) with ESMTP id 1B99E37B422; Sat, 2 Sep 2000 17:12:44 -0700 (PDT) Received: from localhost (galt@localhost) by inconnu.isu.edu (8.9.3/8.9.3) with ESMTP id SAA00625; Sat, 2 Sep 2000 18:12:43 -0600 Date: Sat, 2 Sep 2000 18:12:42 -0600 (MDT) From: John Galt To: Ben Smithurst Cc: Dan Nelson , Mike Meyer , rob , Johannes Zwart , questions@FreeBSD.org Subject: Re: Why not XEmacs, after all? In-Reply-To: <20000902221211.P72445@strontium.scientia.demon.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 2 Sep 2000, Ben Smithurst wrote: > John Galt wrote: > > > So why is it still forbidden in a fresh download? > > 4.0 is 4.0, it won't suddenly change. Ever. If you want to use ports, > cvsup the latest ports tree and you will get no such error. And this somehow makes lynx non-deprecated then? To be more precise, I wanted to use packages, failed, and had to settle with the installed ports tree: this also failed, so I got the tarball and am now using lynx. It's not available "out of the box" in a major version release, this is a result of a policy decision, therefore it may be said that it's deprecated until such a time as it can be proven that the policy no longer is in force: one datum is not enough proof in this case, otherwise one could say that MS-win 3.X was 32-bit, since win 3.11 had some 32-bit components, and there was a backported fix for win 3.1 called win32s. > > I have my own reasons for downloading what I did, > > Let me guess. You want to complain about something which has already > been fixed, and you expect people to be sympathetic? Not really: I EXPECTED lynx. The reason I installed 4.0 is as proof to myself: you see, until last week, I was working on a woefully underpowered system and invested a rather large amount of emotional capital keeping it as updated as possible but consistently failed to install 4.0 (starting sometime about easter...) and keep it alive for an extended amount of time. Last week, I got a new box (new for me...), so I immediately tried my nemisis: 4.0 (you DID ask twice now...). > > > but until the un-forbid fix propagates, > > As it did months ago to those of us who cvsup out ports tree regularly, > you mean? So is 4.0 frozen or dynamic? Or are you not running 4.0 after the first cvs update? If you can't get lynx in 4.0 (not 4.0 plus a couple of things), I still say it's deprecated until I see more than one release reversing the change. -- When you are having a bad day, and it seems like everybody is trying to tick you off, remember that it takes 42 muscles to produce a frown, but only 4 muscles to work the trigger of a good sniper rifle. Who is John galt? Galt@inconnu.isu.edu, that's who! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message