summaryrefslogtreecommitdiff
path: root/mk/bulk/bsd.bulk-pkg.mk
AgeCommit message (Collapse)AuthorFilesLines
2007-03-06The warnings from the wrapper log are added to the report file.rillig1-1/+8
2007-02-19The error output of "make debug" may be useful to know, too.rillig1-2/+2
2007-01-24Quick fix: The main code of the bulk build cannot be run in the shell'srillig1-2/+2
"set -e" mode, since it would fill up the temporary directory. Reverted that change.
2007-01-22A big cleanup:rillig1-66/+40
- The "header" of the build log is always printed, not only when PRECLEAN is set. - The variable "installed" was redundant. Removing it saves 5 lines of code. - When the package is outdated and currently installed, it suffices to just run pkg_delete. The "make deinstall" is too expensive and doesn't do anything further. - Completely rewrote the section that deinstalls unneeded packages. It seems to me that the pkg_info -Q flag has been introduced after the bulk build was initially written, so it wasn't used here. - A package that doesn't get deinstalled with a simple pkg_delete probably has a reason for that. Don't try to run pkg_delete -f after it. - To remove all packages, it isn't necessary to iterate over the installed packages. Just pkg_delete -r "*". - Replaced "required package" with "dependency" in the log messages, since that is shorter. Maybe the term "required package" comes from the time where packages also depended on shared library versions, so that terminology made sense back in 2000. Anyway, that's long ago.
2007-01-15Made the database lookup for deinstalling the unneeded packages lessrillig1-10/+13
obscure by using awk instead of sed.
2007-01-08Packages that are not available on the current platform (and therillig1-2/+14
packages depending on them) are listed in a separate category in the bulk build report.
2006-12-14Use '-o' instead of '-or' in find(1) arguments as the former seems todmcmahill1-2/+2
be more portable (works on at least NetBSD, SunOS-5.9, and Linux). Addressed PR pkg/35245
2006-12-14If a package build fails, append the output of 'make debug' to the logdmcmahill1-2/+5
since sometimes there are questions about various variables and settings. This should help in people trying to investigate build failures.
2006-12-09report correct pkgcount by first cd'ing to PKGDB_DIR, then FINDing in there.jschauma1-2/+2
(else -prune will cause us to return immediately, always reporting 1 installed package even if we have more)
2006-12-09straighten out FIND command to figure out if a package needs to be rebuilt.jschauma1-2/+2
This should fix the problem reported by wiz@.
2006-11-26- Run a single find(1) command to get the list of new files rather than runningjschauma1-4/+4
two finds+two greps. - Run a single find(1) command rather than ls | grep to determine pkg count.
2006-10-13Creating an archive from the working directory may take some time forrillig1-1/+2
big packages, so print an informational message before doing that.
2006-10-07Renamed the "pack" option for _PRESERVE_WRKSRC to "pack-if-failed",rillig1-4/+5
since that's what I really wanted. It's just one day old, so I hope that nobody has gotten used to it.
2006-10-06_PRESERVE_WRKDIR can be set to "pack" to save a .tar.gz archive ofrillig1-3/+10
WRKDIR in the directory where the other log files are.
2006-07-27Whenever we invoke a recursive make, we need to ensure that the properjlam1-14/+14
environment ${PKGSRC_MAKE_ENV} is also passed along. Create a convenience variable RECURSIVE_MAKE that does exactly this and that can be used in place of MAKE when invoking make recursively. Use RECURSIVE_MAKE everywhere in pkgsrc/mk that we invoke make recursively.
2006-07-26When the bulk build code encounters a directory in *SPECIFIC_PKGSwiz1-2/+7
that does not exist, it stopped. Now it instead adds an entry to the main broken file and marks it as not package with maintainer "directory_does_not_exist" in the HTML output. (Not packaged directories are not mentioned in the text version.)
2006-07-03After converting it to HTML format, the build log file is not neededrillig1-1/+2
anymore.
2006-02-13Only write the terminating HTML code to the ${_BROKENFILE} if therillig1-4/+4
package is really broken.
2006-02-11Fixed double quoting of _BROKENWRKLOG.rillig1-2/+2
2006-02-10A small step in the direction of valid HTML for the build log files.rillig1-12/+23
2006-02-10Indented the variable definitions more consistently.rillig1-20/+20
2006-02-04Added the KEEP_BUILDLOGS variable. If it is set to "yes", the build logsrillig1-3/+24
of successful builds are not removed, only renamed. This variable will be useful for examining the warnings that appear during the bulk builds but are thrown away because the package builds fine. This feature is experimental and thus not enabled by default.
2006-02-03If a package is still up to date, it doesn't matter if it is currentlyrillig1-7/+3
installed or not. So there is no need for two different messages. (They had been necessary in revision 1.1, though.)
2006-01-21Fixed pkglint warnings.rillig1-10/+15
2006-01-21- Added a new top level file that saves the REPORT_BASEDIR from the firstrillig1-1/+5
call to the mk/bulk/build script. This is to allow restarting the bulk build without getting confused by the various timestamps that occur during a bulk build. It also fixes some problems where the text/plain report had ended up in a directory different from the other files. - Changed the default filename for the text/plain report from "pkgsrc-results-${BUILDDATE}.txt" to simply "report.txt", as the ${BUILDDATE} variable didn't give a hint to when the bulk build had been started, which is often more important than when the bulk build stopped. - Changed the way to specify the directory and the URL where the bulk build reports are made available. See http://mail-index.netbsd.org/tech-pkg/2005/12/05/0002.html for details. Specifying the directories using the FTPHOST and FTPURL variables will be possible for some months, after which it support for it will be dropped.
2006-01-17`tsort` creates temporary files in the current directory, so change to thejdc1-2/+2
BULKFILESDIR directory before running it. We can now bulk build with a read-only pkgsrc.
2006-01-05Revert unintended part of last commit.joerg1-2/+1
2006-01-05Adjust comment about SUBST_FILES to match reality:joerg1-1/+2
absolute file names work as well.
2005-11-28If the package-specific log directory is empty after building a package,rillig1-1/+5
and ${BULKFILESDIR} != ${PKGSRCDIR}, try to remove the directory.
2005-11-241. Added section headers in the part of the user-settable variables.rillig1-3/+13
2. Reindented two "if" statements that looked like this: if long_long_command; then :; else else_commands fi By just scanning the beginnings of the lines, which is a common way of reading source code, one may easily miss the "hidden" "then" branch at the end of the line. I have changed it to: if long_long_command; then :; else else_commands fi
2005-11-23Changed the file extension of BROKENWRKLOG from ".html" to ".txt". This isrillig1-7/+3
mostly a cosmetic change. The motives for this change are that the HTML files only consisted of "<pre>", the properly quoted text/plain contents and "</pre>". There has been no documentation of reasons for encoding plain text in HTML unnecessarily, so this change will produce text/plain files instead. Another change is that instead of appending to the BROKENWRKSRC, the file is overwritten each time. In a single bulk build this will not change anything. Only when the package is built multiple times in a single bulk build, the behavior will differ. Ok'ed by agc.
2005-11-20Despite having ALLOW_VULNERABLE_PACKAGES in my /etc/mk.conf, I foundagc1-2/+2
that the bulk builds would only work properly with the audit-packages package installed at all times. I am obviously hideously mistaken in this. By popular request, revert the change to add audit-packages, since I am told this is the incorrect way of doing this.
2005-11-19Allow the bulk builds to work by adding security/audit-packages as aagc1-2/+2
BULK_PREREQ package.
2005-11-19Replaced ${ECHO_MSG} with ${ECHO} where appropriate. While there, quotedrillig1-19/+19
the filename of the toplevel BROKENFILE correctly.
2005-11-18Corrected the comment above BULKFILESDIR. It is not only used for therillig1-2/+3
global log files but also for the package-specific ones.
2005-11-18Properly indented preprocessing directives.rillig1-3/+3
2005-11-18Allow FORCEBROKENFILE files to be created in either PKGSRCDIR orrillig1-3/+6
BULKFILESDIR.
2005-11-16Changes for separation of BULKFILESDIR and PKGSRCDIR.rillig1-26/+53
- Added a bunch of internal variables that determine the correct places for the build log files of the current package. - Added section headings. - Moved a sanity check out of the configuration section to not confuse the reader. - mk/bulk/print{depends,index} are called with two arguments, which allows separation of BULKFILESDIR and PKGSRCDIR. - Replaced uses of BUILDLOG, BROKENFILE and BROKENWRKLOG with their internal counterparts, which use ${BULKFILESDIR} instead of ${PKGSRCDIR}.
2005-11-12Fix a typo that in some cases prevented a BROKENFILE from beingkristerw1-2/+2
created.
2005-11-11Remove some redundant printing of messages when we are cleaningkristerw1-6/+2
before/after building the package.
2005-11-11- A warning is printed if there is no PKGNAME matching for a PKGPATH in therillig1-10/+14
.index file. - Condensed the code for printing to another package's .broken file in case of failure. (Added a variable pkg_brokenfile.)
2005-11-11Added two variables BULK_MSG and BULK_MSG_CONT that are used for printingrillig1-45/+54
messages. Replaced all instances of ${ECHO_MSG} "BULK> " with ${BULK_MSG}.
2005-11-10Fixed the remaining instances of code relying on trailing white-space inrillig1-2/+2
the INDEXFILE.
2005-11-10Replaced another instance of grep|awk with a simple awk. A warning isrillig1-3/+3
printed if no package name could be found for a package directory.
2005-11-10Don't rely on the INDEXFILE having trailing white-space in each line.rillig1-2/+2
Whoever had written such unusual code should have left a note in the printindex script that the trailing white-space was required. It is such an uncommon assumption that I treated it as a typo and removed it. Now it's fixed. I also replaced the use of grep|awk with a simple awk, as grep would have interpreted regular expressions in the package name. In general, please think more about _appropriate_ ways to handle data. grep(1) is not a tool for searching strings. It's a tool for searching regular expressions.
2005-11-07Add .forcebroken, a builder-created text file that becomes a PKG_FAIL_REASONtv1-1/+8
if present. By design, it is not cleaned at the start of a bulk build; it is intended to allow a bulk build admin to mark a time-consuming package as not buildable, but which shouldn't be marked permanently as such in the package's Makefile.
2005-11-05Replaced a complicated expression with the equivalent ${PKGWILDCARD}. Addedrillig1-5/+5
the :Q operator to all instances of ${PKGWILDCARD}.
2005-11-05Remove the cleaning of pre-requisite packages before and after buildingkristerw1-19/+7
a package. This functionality consumed an enormous amount and time, and did not do much useful work: * It is not needed when doing a bulk build of the full pkgrsrc tree, since the pre-requisite packages already have been built and cleaned. * It does not work when doing a bulk build of a subset of the packages, since it only cleans the direct dependencies, and not the full list.
2005-10-27Add lang/perl5 early, but not specifically as part of BULK_PREREQ, so thattv1-2/+2
it is available at tflat time.
2005-10-26Use Perl-based tflat, which is up to 90% faster than the awk-based onetv1-11/+6
(necause it was forking off "sort" subprocesses on every package).