From owner-cvs-all Tue Mar 13 16:45:59 2001 Delivered-To: cvs-all@freebsd.org Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id E2D3C37B719; Tue, 13 Mar 2001 16:45:46 -0800 (PST) (envelope-from max@vic.sabbo.net) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.112]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id f2E0jfG28389; Wed, 14 Mar 2001 02:45:43 +0200 Received: (from max@localhost) by vic.sabbo.net (8.11.3/8.11.2) id f2E0jgf15403; Wed, 14 Mar 2001 02:45:42 +0200 (EET) (envelope-from sobomax@FreeBSD.org) From: Maxim Sobolev Message-Id: <200103140045.f2E0jgf15403@vic.sabbo.net> Subject: Re: cvs commit: src/sys/netinet ip_output.c To: paul@originative.co.uk (Paul Richards) Date: Wed, 14 Mar 2001 02:45:42 +0200 (EET) Cc: jkh@osd.bsdi.com (Jordan Hubbard), kris@obsecurity.org, obrien@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org In-Reply-To: <3AAEBD59.1B77E450@originative.co.uk> from "Paul Richards" at Mar 14, 2001 12:37:45 AM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Jordan Hubbard wrote: > > > > > but what about the sysadmin who has to support a real world environment > > > where a product needs to be upgraded to fix a bug, a typical, real world > > > application like say the web server, or database. > > > > The sysadmin who has to do all of that doesn't need the ports > > collection to hold his hand (or some other appendage) just to do > > spot-upgrades of specific pieces. You think Solaris admins never > > upgrade Apache just because they don't have a ports collection? > > The ports collection is one of FreeBSD's big selling points. It's so > comprehensive that it's a real pity when you have to pollute /usr/local/ > on a box with files that aren't under the control of pkg_delete. > > If it's the case that you have to give up on using one of FreeBSD's key > features in order to keep up to date with patches in an application then > that's a big loss in terms of the attractiveness of FreeBSD to the > serious user. I've won around sysadmins to using FreeBSD because of the > ease of maintaining ports but the ease-of-use claims look pretty flimsy > when three months after installation you tell them they have to either > upgrade to the latest FreeBSD release or give up on the ports collection > and go back to doing things by hand if they want to keep up to date with > their application releases. I think that you are overdramatising the whole point. Usually only a very small number of ports broke as the ports tree goes away from your -stable release, and usually if that happens with some of the most-popular apps, like samba or apache, they are quickly getting OSVERSION knobs to build successfully on various -stable incarnations. After all nothing prevents you as a responsible person from fixing it and submitting your fix back as a PR for inclusion into the tree. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message