Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
package since a few days.
|
|
|
|
|
|
|
|
audit-packages.
|
|
|
|
|
|
binary packages has not worked in the last few months. Now I fixed the
rsync command line to use --files-from instead of --include-from, which
does the right thing.
Tested in a directory of about 20 binary packages, including one that is
restricted. Everything worked as expected.
Fixes PR 35199.
|
|
the current working directory.
See http://mail-index.netbsd.org/tech-pkg/2006/08/08/0006.html
|
|
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.
|
|
- 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
|
|
argument list on at least on OS.
|
|
reviewd by joerg.
|
|
during mk/bulk/upload. Disabled by default.
|
|
on Solaris.
|
|
vulnerable packages are uploaded directly into the vulnerable subdir.
While here:
quote variables
better handling of the temporary directory
remove some backwards compatibility code that's been here long enough
opsys-specific package handling was doing the same as non-opsys
specific, so fold them together.
Written together with dillo.
|
|
|
|
(the commented version was committed by mistake)
|
|
files manually.
Suggested and OK'd by jschauma@
|
|
With a slow NFS server (as mine), this can take a lot of time.
|
|
(These are available on all platforms via digest(1).)
Set commands for other checksums on a per OPSYS basis.
Set MKSUSM=yes back as the default.
|
|
packages they upload (by setting the optional variable MKSUMS=yes) and,
also optionally, PGP signing them (by setting SIGN_AS=username@NetBSD.org,
for example).
|
|
"cd" to $USR_PKGSRC automagically so this can be called from any dir.
|
|
by RSYNC_DST. Warn if any of them is not set properly, and in
general adjust to the new layout on the FTP server.
|
|
and run it if it's not explicitly set to "no"
|
|
before trying to upload anything.
|
|
|
|
|
|
|
|
|
|
from pkgsrc current.
|
|
|
|
|
|
|
|
the bulk-install target to work.)
|
|
environment variable, which contains the name of the make(1) program to
invoke - suggestion by Julien Letessier some time ago, the confusion mine,
since I thought he was referring to something else completely.
Don't rely on there being a POSIX tr(1) in the path by default - test
explicitly for both "yes" and "YES".
Set the default for PRUNEDISTFILES to "no", since we can't assume that
the user wants us to delete something which he may have been keeping
around, and there are other ways of accomplishing this aim (lintpkgsrc
-o, for example).
Clean up some superfluous white space at the end of lines.
|
|
references of the pkglint package.
_PKGSRCDIR is an internal definition in bsd.pkg.mk, and a few packages
which would like to refer to other packages in the build tree. It should
not be set by users, but neither should it stop a user from building a
package if it is defined, so make it obvious that this is the case.
|
|
|
|
directory too.
|
|
them in the right place. For example, a collection of binary packages can
now put uploaded with most going to the major.minor directory and the
OSVERSION_SPECIFIC ones going to the major.minor.patch directory.
still todo: the destination settings should probably be moved out of
build.conf so the same build.conf can be used by multiple machines of
different MACHINE_ARCH's at the same time. Perhaps these should be
a command line option to 'upload' instead.
|
|
|