Date: Tue, 13 Mar 2001 21:42:38 -0500 From: "Patrick Bihan-Faou" <patrick@netzuno.com> To: <cvs-all@freebsd.org> Subject: Re: cvs commit: src/sys/netinet ip_output.c Message-ID: <HJEEKLMFLKEOKHOKNPBMMEONCLAA.patrick@netzuno.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?HJEEKLMFLKEOKHOKNPBMMEONCLAA.patrick>