Updating ports svn bsd accommodating my request

15-Feb-2018 05:53

Note on Extreme Sloth: By extreme application of the 'slothful' method of maintenance you could find yourself more that one major version behind (say, using 6.x when the current version is 9.x).The best advice here is to never try a multi-version upgrade, say, from 6.x to 9.x - always pass through the intervening major version(s) - certainly as far as Step 6 since ABI (Application Binary Interface) changes may cause serious problems.In such cases one of the CD based direct install methods may be quicker and less risky.As with all things Free BSD there are about 100,000 million ways of doing things which can leave folk confused when they read three different HOWTOs all describing different ways to accomplish the same goal. The author of the HOWTO has always done it that way.Binary updates (freebsd-update) are supported for this branch only since this constitutes the so called security branch after installation.You can find the information about what version you will have by looking at the script /usr/src/sys/conf/(or in our non-standard case /var/src/sys/conf/newvers.sh) once the svn run is complete.There is no attempt to analyze the reasons - it just works.

Resides in /head, for example, svn.freebsd.org/base/head. Binary updates (freebsd-update) are NOT supported for this tag.Note on the move from CVS to subversion: The notes on manual methods have been updated to reflect the Free BSD change from CVS to subversion that from March 2013 covers both source upgrades and the ports system. We do nothing exciting, nothing even remotely interesting and if it smacks of risk, we lie down in a dark room for a couple of hours, then check that we have access to emergency medical assistance, before doing anything. Free BSD finally stops maintaining our release and we gotta do something. Hell can freeze over before we break that last rule.This survival guide was written because we suspect we are not alone and besides, the down-side of the 'slothful' maintenance theory is we are not constantly doing stuff and so forget....a lot....frequently.We will be using non-standard paths so need we to do more work.If you are using the standard paths ignore commands marked with NON_STD_PATH_ONLY comment below.

Resides in /head, for example, svn.freebsd.org/base/head. Binary updates (freebsd-update) are NOT supported for this tag.Note on the move from CVS to subversion: The notes on manual methods have been updated to reflect the Free BSD change from CVS to subversion that from March 2013 covers both source upgrades and the ports system. We do nothing exciting, nothing even remotely interesting and if it smacks of risk, we lie down in a dark room for a couple of hours, then check that we have access to emergency medical assistance, before doing anything. Free BSD finally stops maintaining our release and we gotta do something. Hell can freeze over before we break that last rule.This survival guide was written because we suspect we are not alone and besides, the down-side of the 'slothful' maintenance theory is we are not constantly doing stuff and so forget....a lot....frequently.We will be using non-standard paths so need we to do more work.If you are using the standard paths ignore commands marked with NON_STD_PATH_ONLY comment below.Some level of risk is involved, offset against being udated for the lastest security fixes, and significantly lower risk than using -CURRENT.