Age | Commit message (Collapse) | Author | Files | Lines |
|
While here, ...
- Added stricter checking by using "set -eu".
- The bulk build configuration file is properly included, and the
MAKECONF definition that it may contain is properly exported.
- All progress messages and error messages are prefixed by "upload>",
so that it is obvious where the messages come from.
- Since extracting the make(1) variables takes quite a long time, print
an informational message before doing that.
- Removed the use of the error-prone lintpkgsrc to detect whether a
package is restricted or vulnerable.
- If an error occurs, the upload program returns an exitcode of 1,
which is common among Unix utilities.
- Removed almost all pipe operators, since they tend to hide program
failures.
- All error messages are redirected to stderr instead of stdout.
|
|
|
|
|
|
whether they may be uploaded, are vulnerable, or good.
|
|
- add a -n|--no-upload flag which does everything but actually executing
the upload to help see what would happen
- add a -d|--debug flag to preserve the temporary files to help with
debugging
- add a -V|--version flag
|
|
- if we can't build one of the required packages, bail out
|
|
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.
|
|
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.)
|
|
anymore.
|
|
argument list on at least on OS.
|
|
build comm/minicom.
|
|
reviewd by joerg.
|
|
during mk/bulk/upload. Disabled by default.
|
|
package is really broken.
|
|
February 2004), so it doesn't conflict with bootstrap-pkgsrc.
|
|
|
|
variable does.
|
|
|
|
|
|
|
|
if it occurs as the condition of a "while" or "if", or in combination
with && or ||. This, of course, introduces a race condition if someone
removes the directory between the two "cd"s. The result would be that
the bulk build terminates, but that's not a big issue, as in this case
there must be something much more severely broken.
|
|
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.
|
|
installed or not. So there is no need for two different messages. (They
had been necessary in revision 1.1, though.)
|
|
${BUILDDATE} before, which has disappeared with the REPORTS_* change.
|
|
activated this prevents unexpected behavior.
|
|
constructing REPORTS_DIR out of FTPHOST and FTPURL.
|
|
with a period.
|
|
|
|
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.
|
|
|
|
BULKFILESDIR directory before running it. We can now bulk build with a
read-only pkgsrc.
|
|
category Makefile. Adjusted the other regular expressions to express more
clearly what is meant.
|
|
- Modified pbc_checkexisting{dir,file} to use pbc_checkpathname.
|
|
|
|
absolute file names work as well.
|
|
|
|
come from.
|
|
|
|
|
|
|
|
much unnecessary redundancy from the code. Reordered the pkgsrc
variables so that related variables appear adjacently in the output.
|
|
from.
|
|
See <http://mail-index.netbsd.org/pkgsrc-bulk/2005/11/24/0003.html>.
|
|
- Removed trailing white-space.
|
|
program if the program would be run in "set -e" mode.
|
|
1. Ensure that it exists before trying to use anything inside of it.
2. Prefix files correctly with BULKFILESDIR to match the rest of
the tree.
3. Most importantly, create the .broken.html files for bootstrap tools
in BULKFILESDIR, otherwise e.g. bmake would be removed in the middle of
a bulk build on non-NetBSD.
Discussed-with: rillig@
|
|
PKG_DELETE and PKG_INFO. This is more straigt-forward and adds the
proper `-K' command line option to the calls, which in turn fixes bulk
builds that don't use the default PKG_DBDIR.
|
|
commit.
|
|
distinguish them from the various other messages.
|
|
quite a long time. Currently the reader of the build log might assume
that the installation of lang/perl5 takes so long, which is wrong.
|