From owner-cvs-all Tue Mar 13 18:41:25 2001 Delivered-To: cvs-all@freebsd.org Received: from VL-MS-MR001.sc1.videotron.ca (relais.videotron.ca [24.201.245.36]) by hub.freebsd.org (Postfix) with ESMTP id 97C1937B71A for ; Tue, 13 Mar 2001 18:41:22 -0800 (PST) (envelope-from patrick@netzuno.com) Received: from jacuzzi ([24.200.106.26]) by VL-MS-MR001.sc1.videotron.ca (Netscape Messaging Server 4.15) with ESMTP id GA624W05.625 for ; Tue, 13 Mar 2001 21:41:20 -0500 Received: from cognac (cognac.local.mindstep.com [192.168.10.4]) by jacuzzi (Postfix) with SMTP id 0CFB13DA5 for ; Tue, 13 Mar 2001 21:43:56 -0500 (EST) From: "Patrick Bihan-Faou" To: Subject: Re: cvs commit: src/sys/netinet ip_output.c Date: Tue, 13 Mar 2001 21:42:38 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > 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. I would add to this that usually by upgrading the /usr/ports/Mk directory, you will solve 99% of the build problems you may encounter when doing the simple: # cd /usr/ports/some/port # cvs update -d -P # make install clean The only rare instances when doing something like did not work for me, I follow this alternate procedure: - update the port on which this one depend - go to /usr/ports/Mk, update - fetch a new shiny port tree It has been my experience that /usr/ports is a (fairly) well behaved autonomous piece that does not depend too much on the host system. Of course there is always some small problems from time to time, but I have only on extremely rare occasions been forced to upgrade the host to be able to build a port (if at all). Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message