From owner-freebsd-ports Tue Mar 31 13:29:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29378 for freebsd-ports-outgoing; Tue, 31 Mar 1998 13:29:57 -0800 (PST) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29306; Tue, 31 Mar 1998 13:29:47 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id NAA05335; Tue, 31 Mar 1998 13:29:23 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: shimon@simon-shapiro.org cc: asami@FreeBSD.ORG (Satoshi Asami), deischen@iworks.InterWorks.org, freebsd-ports@FreeBSD.ORG Subject: Re: editor/nedit patching fails In-reply-to: Your message of "Tue, 31 Mar 1998 09:59:34 PST." Date: Tue, 31 Mar 1998 13:29:23 -0800 Message-ID: <5331.891379763@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Which indicates environmental deltas. If I follow the procedure and it > breaks, the procedure is broken. Either by not checking or by not setting > the environment properly. Example, if I supposedly have the wrong version > of patch(1), then the port is sensitive to patch version and should check > for it. Or you need to make sure that your installation of 3.0 is a _clean_ (that is, from scratch) installation since that's the "target market" at which 3.0 will eventually be aimed. There's so much that's changed between 2.x and 3.0, it might not even be possible to offer an automated upgrade for it (at least not one without lots of specialized intelligence, anyway). Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message