From owner-svn-doc-projects@FreeBSD.ORG Sat Jan 12 19:14:58 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3797D724; Sat, 12 Jan 2013 19:14:58 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 219DB683; Sat, 12 Jan 2013 19:14:58 +0000 (UTC) Received: from svn.freebsd.org (svn.FreeBSD.org [8.8.178.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0CJEwu0037936; Sat, 12 Jan 2013 19:14:58 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0CJEvon037931; Sat, 12 Jan 2013 19:14:57 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201301121914.r0CJEvon037931@svn.freebsd.org> From: Glen Barber Date: Sat, 12 Jan 2013 19:14:57 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r40581 - in projects/entities/en_US.ISO8859-1: articles/contributors articles/geom-class articles/portbuild articles/solid-state books/arch-handbook/driverbasics books/faq books/fdp-pri... X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Jan 2013 19:14:58 -0000 Author: gjb Date: Sat Jan 12 19:14:56 2013 New Revision: 40581 URL: http://svnweb.freebsd.org/changeset/doc/40581 Log: Merged /head/en_US.ISO8859-1:r40371-40577 Added: projects/entities/en_US.ISO8859-1/htdocs/4xx.xml - copied unchanged from r40577, head/en_US.ISO8859-1/htdocs/4xx.xml projects/entities/en_US.ISO8859-1/htdocs/releases/9.1R/announce.xml - copied unchanged from r40577, head/en_US.ISO8859-1/htdocs/releases/9.1R/announce.xml projects/entities/en_US.ISO8859-1/htdocs/releases/9.1R/errata.html - copied unchanged from r40577, head/en_US.ISO8859-1/htdocs/releases/9.1R/errata.html projects/entities/en_US.ISO8859-1/htdocs/releases/9.1R/hardware.html - copied unchanged from r40577, head/en_US.ISO8859-1/htdocs/releases/9.1R/hardware.html projects/entities/en_US.ISO8859-1/htdocs/releases/9.1R/installation.html - copied unchanged from r40577, head/en_US.ISO8859-1/htdocs/releases/9.1R/installation.html projects/entities/en_US.ISO8859-1/htdocs/releases/9.1R/readme.html - copied unchanged from r40577, head/en_US.ISO8859-1/htdocs/releases/9.1R/readme.html projects/entities/en_US.ISO8859-1/htdocs/releases/9.1R/relnotes-detailed.html - copied unchanged from r40577, head/en_US.ISO8859-1/htdocs/releases/9.1R/relnotes-detailed.html projects/entities/en_US.ISO8859-1/htdocs/releases/9.1R/relnotes.xml - copied unchanged from r40577, head/en_US.ISO8859-1/htdocs/releases/9.1R/relnotes.xml Deleted: projects/entities/en_US.ISO8859-1/htdocs/layout/images/front_get_back.png projects/entities/en_US.ISO8859-1/htdocs/layout/images/front_get_bl.png projects/entities/en_US.ISO8859-1/htdocs/layout/images/front_get_br.png projects/entities/en_US.ISO8859-1/htdocs/layout/images/front_get_tl.png projects/entities/en_US.ISO8859-1/htdocs/layout/images/front_get_tr.png projects/entities/en_US.ISO8859-1/htdocs/layout/images/front_new_back.png projects/entities/en_US.ISO8859-1/htdocs/layout/images/front_new_bl.png projects/entities/en_US.ISO8859-1/htdocs/layout/images/front_new_br.png projects/entities/en_US.ISO8859-1/htdocs/layout/images/front_new_tl.png projects/entities/en_US.ISO8859-1/htdocs/layout/images/front_new_tr.png Modified: projects/entities/en_US.ISO8859-1/articles/contributors/contrib.additional.xml projects/entities/en_US.ISO8859-1/articles/contributors/contrib.committers.xml projects/entities/en_US.ISO8859-1/articles/geom-class/article.xml projects/entities/en_US.ISO8859-1/articles/portbuild/article.xml projects/entities/en_US.ISO8859-1/articles/solid-state/article.xml projects/entities/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml projects/entities/en_US.ISO8859-1/books/faq/book.xml projects/entities/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.xml projects/entities/en_US.ISO8859-1/books/handbook/book.xml projects/entities/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml projects/entities/en_US.ISO8859-1/books/handbook/desktop/chapter.xml projects/entities/en_US.ISO8859-1/books/handbook/eresources/chapter.xml projects/entities/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml projects/entities/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml projects/entities/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml projects/entities/en_US.ISO8859-1/books/handbook/ports/chapter.xml projects/entities/en_US.ISO8859-1/books/handbook/x11/chapter.xml projects/entities/en_US.ISO8859-1/books/porters-handbook/book.xml projects/entities/en_US.ISO8859-1/htdocs/Makefile projects/entities/en_US.ISO8859-1/htdocs/applications.xml projects/entities/en_US.ISO8859-1/htdocs/cgi/cgi-style.pl projects/entities/en_US.ISO8859-1/htdocs/cgi/man.cgi projects/entities/en_US.ISO8859-1/htdocs/community.xsl projects/entities/en_US.ISO8859-1/htdocs/copyright/Makefile projects/entities/en_US.ISO8859-1/htdocs/copyright/copyright.xml projects/entities/en_US.ISO8859-1/htdocs/copyright/freebsd-doc-license.xml projects/entities/en_US.ISO8859-1/htdocs/copyright/freebsd-license.xml projects/entities/en_US.ISO8859-1/htdocs/events/Makefile projects/entities/en_US.ISO8859-1/htdocs/index.xsl projects/entities/en_US.ISO8859-1/htdocs/layout/css/fixed.css projects/entities/en_US.ISO8859-1/htdocs/layout/css/layout.css projects/entities/en_US.ISO8859-1/htdocs/layout/images/Makefile projects/entities/en_US.ISO8859-1/htdocs/news/2012-compromise.xml projects/entities/en_US.ISO8859-1/htdocs/releases/9.1R/Makefile projects/entities/en_US.ISO8859-1/htdocs/releases/9.1R/schedule.xml projects/entities/en_US.ISO8859-1/htdocs/releases/index.xml projects/entities/en_US.ISO8859-1/htdocs/releng/index.xml projects/entities/en_US.ISO8859-1/htdocs/search/index-site.xsl projects/entities/en_US.ISO8859-1/htdocs/security/security.xml projects/entities/en_US.ISO8859-1/htdocs/snapshots/index.xml projects/entities/en_US.ISO8859-1/htdocs/where.xml projects/entities/en_US.ISO8859-1/share/xml/mailing-lists.ent Directory Properties: projects/entities/en_US.ISO8859-1/ (props changed) Modified: projects/entities/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- projects/entities/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Sat Jan 12 19:14:31 2013 (r40580) +++ projects/entities/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Sat Jan 12 19:14:56 2013 (r40581) @@ -2416,18 +2416,23 @@ + David Vachulka + arch_dvx@users.sourceforge.net + + + David Wolfskill david@catwhisker.org - Dax Labrador - semprix@bsdmail.org + David Yeske + dyeske@yahoo.com - David Yeske - dyeske@yahoo.com + Dax Labrador + semprix@bsdmail.org @@ -3093,6 +3098,11 @@ + Fabian M. Borschel + fmb@onibox.net + + + Fabien Devaux fab@gcu.info @@ -10528,6 +10538,11 @@ + Victor Popov + v.a.popov@gmail.com + + + Victor Semionov semionov@mail.bg Modified: projects/entities/en_US.ISO8859-1/articles/contributors/contrib.committers.xml ============================================================================== --- projects/entities/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Sat Jan 12 19:14:31 2013 (r40580) +++ projects/entities/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Sat Jan 12 19:14:56 2013 (r40581) @@ -624,6 +624,10 @@ + &a.markj.email; + + + &a.tj.email; Modified: projects/entities/en_US.ISO8859-1/articles/geom-class/article.xml ============================================================================== --- projects/entities/en_US.ISO8859-1/articles/geom-class/article.xml Sat Jan 12 19:14:31 2013 (r40580) +++ projects/entities/en_US.ISO8859-1/articles/geom-class/article.xml Sat Jan 12 19:14:56 2013 (r40581) @@ -92,7 +92,7 @@ The &man.style.9; man page — for documentation on the coding-style conventions which must be followed for any code - which is to be committed to the FreeBSD CVS tree. + which is to be committed to the FreeBSD Subversion tree. Modified: projects/entities/en_US.ISO8859-1/articles/portbuild/article.xml ============================================================================== --- projects/entities/en_US.ISO8859-1/articles/portbuild/article.xml Sat Jan 12 19:14:31 2013 (r40580) +++ projects/entities/en_US.ISO8859-1/articles/portbuild/article.xml Sat Jan 12 19:14:56 2013 (r40581) @@ -24,6 +24,7 @@ 2010 2011 2012 + 2013 The &os; Ports Management Team @@ -50,61 +51,64 @@ . This article documents the internal workings of the - cluster. + cluster. Many of the details in this article will be of interest only to - those on the Ports Management - team. + those on the Ports Management + team. The codebase - Most of the package building magic occurs under the - /var/portbuild directory. Unless - otherwise specified, all paths will be relative to - this location. ${arch} will - be used to specify one of the package architectures - (e.g., amd64, arm, &i386;, ia64, powerpc, &sparc64;), and - ${branch} will be used - to specify the build branch (e.g., 7, 7-exp, 8, 8-exp, 9, 9-exp, 10, 10-exp). - The set of branches that portmgr currently - supports is the same as those that the &os; - security team - supports. - - - - Packages are no longer built for branches 4, 5, or 6, nor - for the alpha architecture. - - - The scripts that control all of this live in - /var/portbuild/scripts/. - These are the checked-out copies from the Subversion repository at - - base/projects/portbuild/scripts/ - . - - Typically, incremental builds are done that use previous - packages as dependencies; this takes less time, and puts less - load on the mirrors. Full builds are usually only done: + Most of the package building magic occurs under the + /var/portbuild directory. Unless + otherwise specified, all paths will be relative to + this location. ${arch} will + be used to specify one of the package architectures + (e.g., amd64, arm, &i386;, ia64, powerpc, &sparc64;), and + ${branch} will be used + to specify the build branch (e.g., 7, 7-exp, 8, 8-exp, 9, 9-exp, 10, 10-exp). + The set of branches that portmgr currently + supports is the same as those that the &os; + security team + supports. + - - right after release time, for the - -STABLE branches + + Packages are no longer built for branches 4, 5, or 6, nor + for the alpha architecture. + - periodically to test changes to - -CURRENT - + The scripts that control all of this live in + /var/portbuild/scripts/. + These are the checked-out copies from the Subversion repository at + + base/projects/portbuild/scripts/ + . + + Typically, incremental builds are done that use previous + packages as dependencies; this takes less time, and puts less + load on the mirrors. Full builds are usually only done: - for experimental ("exp-") builds + + + right after release time, for the + -STABLE branches + - + + periodically to test changes to + -CURRENT + - Packages from experimental builds are not uploaded. + + for experimental ("exp-") builds + + + Packages from experimental builds are not uploaded. @@ -116,38 +120,44 @@ for other hosts to be head nodes. Among the changes were: - removal of the hard-coding of the string - pointyhat + + removal of the hard-coding of the string + pointyhat + - factoring out all configuration constants (which - were previously scattered throughout the code) into configuration - files (see below) - - - appending the hostname to the directories - specified by buildid (this will allow - directories to be unambigious when copied between machines.) - + + factoring out all configuration constants (which + were previously scattered throughout the code) into configuration + files (see below) + - making the scripts more robust in terms of setting - up directories and symlinks + + appending the hostname to the directories + specified by buildid (this will allow + directories to be unambigious when copied between machines.) + - where necessary, changing certain script invocations - to make all the above easier + + making the scripts more robust in terms of setting + up directories and symlinks + + + where necessary, changing certain script invocations + to make all the above easier + This document was originally written before these changes were made. Where things such as script invocations have changed, - they are denoted as new codebase: as opposed + they were denoted as new codebase: as opposed to old codebase:. Up until November 2012, pointyhat had still been running the old codebase. That installation has now been permanently offlined. Therefore, all the instructions having - to do with the old codebase are obsolete, - and will be removed in the near future. + to do with the old codebase have been removed. @@ -221,24 +231,16 @@ The bindist.tar file is extracted onto each client at client boot time, and at the start of each pass of the dopackages - script. - - - - New Codebase + script. - For both commands above, if - ${buildid} is - latest, it may be omitted. - - + For both commands above, if + ${buildid} is + latest, it may be omitted. Customizing Your Build - (The following only applies to the new codebase.) - You can customize your build by providing local versions of make.conf and/or src.conf, @@ -291,8 +293,7 @@ (For this case, the contents are also identical for both server and client.) - -.if !defined(CC) || ${CC} == "cc" + .if !defined(CC) || ${CC} == "cc" CC=clang .endif .if !defined(CXX) || ${CXX} == "c++" @@ -303,8 +304,7 @@ CPP=clang-cpp .endif # Do not die on warnings NO_WERROR= -WERROR= - +WERROR= @@ -348,365 +348,260 @@ PKG_BIN=/usr/local/sbin/pkg <command>dopackages</command> scripts - The scripts/dopackages scripts - are used to perform the builds. - - - Old codebase - For the old codebase: the - most useful are: - - - - dopackages.7 - Perform - a 7.X build - - - - - dopackages.7-exp - Perform - a 7.X build with experimental patches - (7-exp branch) - - - - - dopackages.8 - Perform - a 8.X build - - - - - dopackages.8-exp - Perform - a 8.X build with experimental patches - (8-exp branch) - - - - - dopackages.9 - Perform - a 9.X build - - - - - dopackages.9-exp - Perform - a 9.X build with experimental patches - (9-exp branch) - - - - - dopackages.10 - Perform - a 10.X build - - - - - dopackages.10-exp - Perform - a 10.X build with experimental patches - (10-exp branch) - - - - - These are wrappers around dopackages, - and are all symlinked to dopackages.wrapper. - New branch wrapper scripts can be created by symlinking - dopackages.${branch} to - dopackages.wrapper. These scripts - take a number of arguments. For example: - - dopackages.7 ${arch} ${buildid} [-options] - - - - - New codebase - The symlinks go away, and you just use - dopackages.wrapper directly. For example: + The scripts/dopackages.wrapper script + is used to perform the builds. - &prompt.root; dopackages.wrapper ${arch} ${branch} ${buildid} [-options] + &prompt.root; dopackages.wrapper ${arch} ${branch} ${buildid} - - - - Either codebase - - Most often, you will be using latest for - the value of buildid. - - [-options] may be zero or more of the - following: - - - - -keep - Do not delete this build in the - future, when it would be normally deleted as part of the - latest - previous cycle. - Do not forget to clean it up manually when you no longer need it. - - + Most often, you will be using latest for + the value of buildid. - - -nofinish - Do not perform - post-processing once the build is complete. Useful - if you expect that the build will need to be restarted - once it finishes. If you use this option, do not forget to cleanup - the clients when you do not need the build any more. - - + [-options] may be zero or more of the + following: - - -finish - Perform - post-processing only. - - + + + - Do not delete this build in the + future, when it would be normally deleted as part of the + latest - previous cycle. + Do not forget to clean it up manually when you no longer need it. + - - -nocleanup - By default, when the - -finish stage of the build is complete, the build - data will be deleted from the clients. This option will prevent - that. - + + - Do not perform + post-processing once the build is complete. Useful + if you expect that the build will need to be restarted + once it finishes. If you use this option, do not forget to cleanup + the clients when you do not need the build any more. + - - -restart - Restart an interrupted - (or non-finished) build from the - beginning. Ports that failed on the previous build will - be rebuilt. - - + + - Perform + post-processing only. + - - -continue - Restart an interrupted - (or non-finished) build. Will not - rebuild ports that failed on the previous build. - - + + - By default, when the + stage of the build is complete, the build + data will be deleted from the clients. This option will prevent + that. + - - -incremental - Compare the - interesting fields of the new - INDEX with the previous one, - remove packages and log files for the old ports that - have changed, and rebuild the rest. This - cuts down on build times substantially since - unchanged ports do not get rebuilt every time. - - + + - Restart an interrupted + (or non-finished) build from the + beginning. Ports that failed on the previous build will + be rebuilt. + - - -cdrom - This package build is - intended to end up on a CD-ROM, so - NO_CDROM packages and distfiles - should be deleted in post-processing. - - + + - Restart an interrupted + (or non-finished) build. Will not + rebuild ports that failed on the previous build. + - - -nobuild - Perform all - the preprocessing steps, but do not actually do - the package build. - - + + - Compare the + interesting fields of the new + INDEX with the previous one, + remove packages and log files for the old ports that + have changed, and rebuild the rest. This + cuts down on build times substantially since + unchanged ports do not get rebuilt every time. + - - -noindex - Do not rebuild - INDEX during preprocessing. - - + + - This package build is + intended to end up on a CD-ROM, so + NO_CDROM packages and distfiles + should be deleted in post-processing. + - - -noduds - Do not rebuild the - duds file (ports that are never - built, e.g., those marked IGNORE, - NO_PACKAGE, etc.) during - preprocessing. - - + + - Perform all + the preprocessing steps, but do not actually do + the package build. + - - -nochecksubdirs - Do not check the - SUBDIRS for ports that are not connected - to the build. (New codebase only). - - + + - Do not rebuild + INDEX during preprocessing. + - - -trybroken - Try to build - BROKEN ports (off by default - because the amd64/&i386; clusters are fast enough now - that when doing incremental builds, more time - was spent rebuilding things that were going to - fail anyway. Conversely, the other clusters - are slow enough that it would be a waste of time - to try and build BROKEN ports). - - - With -trybroken, you probably - also want to use -fetch-original - (and, on the new codebase, - -unlimited-errors). - - + + - Do not rebuild the + duds file (ports that are never + built, e.g., those marked IGNORE, + NO_PACKAGE, etc.) during + preprocessing. + - - -nosrc - Do not update the - src tree from the ZFS snapshot, keep the tree from - previous build instead. - - + + - Do not check the + SUBDIRS for ports that are not connected + to the build. + - - -srcvcs - Do not update the - src tree from the ZFS snapshot, update it with - a fresh checkout instead. - - + + - Try to build + BROKEN ports (off by default + because the amd64/&i386; clusters are fast enough now + that when doing incremental builds, more time + was spent rebuilding things that were going to + fail anyway. Conversely, the other clusters + are slow enough that it would be a waste of time + to try and build BROKEN ports). - - -noports - Do not update the - ports tree from the ZFS snapshot, keep the tree from - previous build instead. - - + + With , you probably + also want to use + and + . + + - - -portsvcs - Do not update the - ports tree from the ZFS snapshot, update it with - a fresh checkout instead. - - + + - Do not update the + src tree from the ZFS snapshot, keep the tree from + previous build instead. + - - -norestr - Do not attempt to build - RESTRICTED ports. - - + + - Do not update the + src tree from the ZFS snapshot, update it with + a fresh checkout instead. + - - -noplistcheck - Do not make it fatal for - ports to leave behind files after deinstallation. - - + + - Do not update the + ports tree from the ZFS snapshot, keep the tree from + previous build instead. + - - -nodistfiles - Do not collect distfiles - that pass make checksum for later - uploading to ftp-master. - - + + - Do not update the + ports tree from the ZFS snapshot, update it with + a fresh checkout instead. + - - -fetch-original - Fetch the - distfile from the original MASTER_SITES - rather than any cache such as on ftp-master. - - + + - Do not attempt to build + RESTRICTED ports. + - - -unlimited-errors (new codebase - only) - defeat the "qmanager threshhold" check for runaway - builds. You want this primarily when doing a - -restart of a build that you expect to mostly - fail, or perhaps a -trybroken run. By default, - the threshhold check is done. - - + + - Do not make it fatal for + ports to leave behind files after deinstallation. + - Unless you specify -restart, - -continue, or -finish, - the symlinks for the existing builds will be rotated. i.e, - the existing symlink for previous will - be deleted; the most recent build will have its symlink changed - to previous/; and a new build will be - created and symlinked into latest/. - + + - Do not collect distfiles + that pass make checksum for later + uploading to ftp-master. + - If the last build finished cleanly you do not need to delete - anything. If it was interrupted, or you selected - -nocleanup, you need to clean up clients by running - + + - Fetch the + distfile from the original MASTER_SITES + rather than any cache such as on ftp-master. + - &prompt.user; build cleanup ${arch} ${branch} ${buildid} -full + + + - defeat the "qmanager threshhold" check for runaway + builds. You want this primarily when doing a + of a build that you expect to mostly + fail, or perhaps a run. By default, + the threshhold check is done. + + - When a new build is created, the directories errors/, - logs/, packages/, and so - forth, are cleaned by the scripts. If you are short of space, - you can also clean out ports/distfiles/. - Leave the latest/ directory alone; it is - a symlink for the webserver. + Unless you specify , + , or , + the symlinks for the existing builds will be rotated. i.e, + the existing symlink for previous will + be deleted; the most recent build will have its symlink changed + to previous/; and a new build will be + created and symlinked into latest/. + + If the last build finished cleanly you do not need to delete + anything. If it was interrupted, or you selected + , you need to clean up clients by running + + &prompt.user; build cleanup ${arch} ${branch} ${buildid} -full + + When a new build is created, the directories errors/, + logs/, packages/, and so + forth, are cleaned by the scripts. If you are short of space, + you can also clean out ports/distfiles/. + Leave the latest/ directory alone; it is + a symlink for the webserver. - - dosetupnodes is supposed to be run from - the dopackages script in the - -restart case, but it can be a good idea to - run it by hand and then verify that the clients all have the - expected job load. Sometimes, - dosetupnode cannot clean up a build and you - need to do it by hand. (This is a bug.) - + + dosetupnodes is supposed to be run from + the dopackages script in the + case, but it can be a good idea to + run it by hand and then verify that the clients all have the + expected job load. Sometimes, + dosetupnode cannot clean up a build and you + need to do it by hand. (This is a bug.) + - Make sure the ${arch} build - is run as the ports-${arch} user - or it will complain loudly. - - The actual package build itself occurs in two - identical phases. The reason for this is that sometimes - transient problems (e.g., NFS failures, FTP sites being - unreachable, etc.) may halt a build. Doing things - in two phases is a workaround for these types of - problems. - - Be careful that ports/Makefile - does not specify any empty subdirectories. This is especially - important if you are doing an -exp build. If the build - process encounters an empty subdirectory, both package build - phases will stop short, and an error similar to the following - will be written to - ${arch}/${branch}/journal: - + Make sure the ${arch} build + is run as the ports-${arch} user + or it will complain loudly. - don't know how to make dns-all(continuing) + + The actual package build itself occurs in two + identical phases. The reason for this is that sometimes + transient problems (e.g., NFS failures, FTP sites being + unreachable, etc.) may halt a build. Doing things + in two phases is a workaround for these types of + problems. + - To correct this problem, simply comment out or remove - the SUBDIR entries that point to empty - subdirectories. After doing this, you can restart the build - by running the proper dopackages command - with the -restart option. - + Be careful that ports/Makefile + does not specify any empty subdirectories. This is especially + important if you are doing an -exp build. If the build + process encounters an empty subdirectory, both package build + phases will stop short, and an error similar to the following + will be written to + ${arch}/${branch}/journal: + + don't know how to make dns-all(continuing) + + To correct this problem, simply comment out or remove + the SUBDIR entries that point to empty + subdirectories. After doing this, you can restart the build + by running the proper dopackages command + with the option. - - This problem also appears if you create a new category - Makefile with no SUBDIRs - in it. This is probably a bug. - + + This problem also appears if you create a new category + Makefile with no SUBDIRs + in it. This is probably a bug. + - - Update the i386-7 tree and do a complete build + + Update the i386-7 tree and do a complete build - &prompt.user; dopackages.7 i386 -nosrc -norestr -nofinish -&prompt.user; dopackages.wrapper i386 7 -nosrc -norestr -nofinish - + &prompt.user; dopackages.wrapper i386 7 -nosrc -norestr -nofinish + - - Restart an interrupted amd64-8 build without updating + + Restart an interrupted amd64-8 build without updating - &prompt.user; dopackages.8 amd64 -nosrc -noports -norestr -continue -noindex -noduds -nofinish -&prompt.user; dopackages.wrapper amd64 8 -nosrc -noports -norestr -continue -noindex -noduds -nofinish - + &prompt.user; dopackages.wrapper amd64 8 -nosrc -noports -norestr -continue -noindex -noduds -nofinish + - - Post-process a completed sparc64-7 tree + + Post-process a completed sparc64-7 tree - &prompt.user; dopackages.7 sparc64 -finish -&prompt.user; dopackages.wrapper sparc64 7 -finish - + &prompt.user; dopackages.wrapper sparc64 7 -finish + - Hint: it is usually best to run the dopackages - command inside of screen(1). - + Hint: it is usually best to run the dopackages + command inside of screen(1). @@ -723,10 +618,7 @@ PKG_BIN=/usr/local/sbin/pkgbranch [newid] - Creates newid (or a datestamp if not specified). - Only needed when bringing up a new branch or a new architecture. - (TODO: document whether newid must be specified as - latest in the new codebase.) - + Only needed when bringing up a new branch or a new architecture. @@ -734,8 +626,7 @@ PKG_BIN=/usr/local/sbin/pkgbranch oldid [newid] - Clones oldid to - newid (or a datestamp if not specified). - + newid (or a datestamp if not specified). @@ -744,8 +635,7 @@ PKG_BIN=/usr/local/sbin/pkgbuildid - Replaces the src tree with a new ZFS snapshot. Do not forget to use -nosrc flag to dopackages - later! - + later! @@ -754,10 +644,8 @@ PKG_BIN=/usr/local/sbin/pkgbuildid - Replaces the ports tree with a new ZFS snapshot. Do not forget to use -noports flag to dopackages - later! - + later! - @@ -768,7 +656,7 @@ PKG_BIN=/usr/local/sbin/pkg - &prompt.root; path/qmanager/packagebuild amd64 7-exp 20080904212103 aclock-0.2.3_2.tbz + &prompt.root; path/qmanager/packagebuild amd64 7-exp 20080904212103 aclock-0.2.3_2.tbz @@ -781,88 +669,72 @@ PKG_BIN=/usr/local/sbin/pkg - An update of the current ports - tree from the ZFS snapshot [*] - + An update of the current ports + tree from the ZFS snapshot + Status of these steps can be found in + ${arch}/${branch}/build.log + as well as on stderr of the tty running the + dopackages command. An update of the running branch's - src tree from the ZFS snapshot [*] - + src tree from the ZFS snapshot Checks which ports do not have a - SUBDIR entry in their respective - category's Makefile [*] - + SUBDIR entry in their respective + category's Makefile Creates the duds file, which - is a list of ports not to build [*] [+] - + is a list of ports not to build + If any of these steps fail, the build will stop + cold in its tracks. Generates a fresh INDEX - file [*] [+] - + file Sets up the nodes that will be used in the - build [*] [+] - + build - Builds a list of restricted ports [*] [+] + Builds a list of restricted ports *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***