From owner-freebsd-advocacy Mon Mar 8 21:15: 0 1999 Delivered-To: freebsd-advocacy@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id E8C6514FD6 for ; Mon, 8 Mar 1999 21:14:20 -0800 (PST) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.6) id WAA07729; Mon, 8 Mar 1999 22:13:55 -0700 (MST) Message-Id: <4.1.19990308213030.03ea5c80@localhost> Message-Id: <4.1.19990308213030.03ea5c80@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 08 Mar 1999 21:36:39 -0700 To: Bill Fumerola From: Brett Glass Subject: Ports Cc: Brett Taylor , Adam Turoff , freebsd-advocacy@FreeBSD.ORG In-Reply-To: References: <4.1.19990302163944.00a1e620@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:32 PM 3/3/99 -0500, Bill Fumerola wrote: >If the users aren't updating their sources/ports, then the new (lack of) >support will not alienate them. They're often adding the port for the first time. Suddenly, they want a Web server, a new editor, a network utility. They get an old one with security holes. Not good. I want to be able to tell my system, "I want the latest version of Program X for the version of the operating system I'm currently running. Make it so." There's no reason why the ports collection can't resolve the dependencies and do that. >Either > Users want new/updated ports, and they keep their source current. Non sequitur. I don't want to have a "versionless" or unstable version of the OS on the machine just to get a recent version of a ported app. As it is, I often forego the ports collection altogether and compile the app myself. This can cause problems because I won't be able to take care of any necessary adaptations that would be made in a port. If someone out there is taking the time to do builds, I should be able to use them. Otherwise, the port maintainer's time and effort are not being used effectively to bring the most benefit to users. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message