Age | Commit message (Collapse) | Author | Files | Lines |
|
revision 1.68
date: 2006/03/17 02:31:44; author: hubertf; state: Exp; lines: +4 -3
pkg_do(): only use cp2 if it's really set to something useful
Coverity CID 1176
|
|
revision 1.36
date: 2005/12/03 01:08:38; author: hubertf; state: Exp; lines: +3 -3
Only warn about running as non-root when -v is given
(or when running in non-unprivilegedmode, but how to detect?)
|
|
revision 1.51
date: 2006/03/06 20:00:10; author: reed; state: Exp; lines: +4 -4
Fix the "Cannot chdir" error message to actually show the
problem directory name for lsbest and lsall.
For example:
# pkg_admin -d /usr/packages/DragonFly/1.4.0/i386/All lsbest 'gmake>0'
pkg_admin: Cannot chdir to /var/db/pkg: No such file or directory
Should show:
pkg_admin: Cannot chdir to /usr/packages/DragonFly/1.4.0/i386/All: No such file or directory
|
|
revision 1.117
date: 2006/03/17 02:37:31; author: hubertf; state: Exp; lines: +6 -2
Add sanity check if there's a @cwd in the +CONTENT file.
If not abort, because we wouldn't know where to put the files.
Coverity CID 1358
|
|
even if the initial package to install isn't installed yet.
Bump the version to 20060313.
|
|
for the sake of compatibility tests in pkg_add.
E.g. DragonFly versions like
1.4.0-RELEASE
are reduced to
1.4.0
This code is currently enabled for DragonFly only.
|
|
Use MaxPathSize instead of PATH_MAX.
|
|
- if you have > db1 the probably you have db_185.h which means
that dbopen is really __db185_open, and we'll prefer that.
- else if you have db1, then you have db1/db.h and dbopen
- else if you have db.h, then this is either the one from db1 and it will
work with -ldb having dbopen, or it will not.
Note that the compatibility option on __db185_open() will actually not create
or update db1.85/1.86 files, but it will use the current format of the db
library. This compatibility layer is source code only.
|
|
(pkg_do) When marking already installed package as manually installed,
only print message if we succeeded.
Noted by wiz.
|
|
Modify pfcexec so the new process file name can be different from argv[0].
This fix is from Peter Postma, and it addresses PR#32228
|
|
|
|
Addresses PR#32149
|
|
|
|
and add PAX_CMD fallback macro.
|
|
problems. Instead, use exec*() functions.
Replace PUSHOUT() macro and string buffers with a function that
operates on data structures.
If it is necessary to copy files into place from staging area, then use
pax to copy them.
Add functions in pexec.c to create a pipe for sending data to a child
process. Replace pipe code in create/perform.c with these functions.
Use these functions instead of command-line arguments when copying files
into place from staging area.
Three system() references remain: @exec, @unexec, and vsystem().
|
|
Fix first part of PR 32068: pkg_info -Q broken for local binary packages
Add BUILD_INFO_FNAME to the files to extract for SHOW_BI_VAR.
Bump version.
|
|
Fixes PR 32071 by HEO SeonMeyong.
|
|
from dewey_match in pmatch.
|
|
|
|
Remove some unnecessary header includes.
|
|
|
|
Replace wait(2) with equivalent waitpid(2); for Linux, reported by wulf@
on tech-pkg.
|
|
(Insert config.h, nbcompat.h, and bracket the other includes with
#if HAVE_<file>.)
|
|
|
|
|
|
|
|
Welcome to 20051103!
Now with "automatic" support.
|
|
can hang.
Submitted-by: Eirik Nygaard
|
|
| Modified Files:
| src/usr.sbin/pkg_install/add: perform.c
|
| Log Message:
| cleanup: preserve errno. Needed so err() functions ran after running
| cleanup(0) print the correct error message.
|
|
| To generate a diff of this commit:
| cvs rdiff -r1.109 -r1.110 src/usr.sbin/pkg_install/add/perform.c
|
|
| Modified Files:
| src/usr.sbin/pkg_install/add: extract.c
|
| Log Message:
| Fix 'pkg_add -R' handling - not registering really means not touching
| the pkgdb too - useful for pkg_add as non-root!
|
|
| To generate a diff of this commit:
| cvs rdiff -r1.34 -r1.35 src/usr.sbin/pkg_install/add/extract.c
|
|
Warn, but don't error out on pkgs that were built with IGNORE_RECOMMENDED.
Bump version to 20050718.
|
|
in AIX-4.3.2) PRIu64. If it is missing or broken, provide one. Should
address PR30375. Welcome to pkg_install-20050607
|
|
|
|
|
|
Sync with base system: Ranges support and some other stuff that wasn't
pulled over.
|
|
If a pattern does not have any suffix, assume that it matches both
".tbz" and ".tgz". This allows to install binary package dependencies
that are not exact matches, but satisfy requirements.
|
|
of a 32 bit signed number when pkg_add-ing a binary package
file larger than 512 Mb.
- Bump PKGTOOLS_VERSION (NOT!!! PKGTOOLS_REQD) to 20050527
|
|
happened to me when I had a misnamed directory in the pkgdb directory.
|
|
|
|
* ftp.fi.netbsd.org returns "257" in return to a "cd" command, accept that
(in addition to 250 and 550). Seems to be allowed per RFC 959.
* Make buffer for reply bigger (not too big, as it may hit performance).
* Bump PKGTOOLS_VERSION (NOT!!! PKGTOOLS_REQD) to 20050318
|
|
by wiz.
|
|
+ state that the message is just a warning
+ make it clearer what an OS mismatch is
|
|
initialise a variable before using it. pkg_info binpkg.tgz would pass
garbage on the command line to tar(1).
|
|
cast return value of min_free() to uint64_t.
fixes pkg_add <binarypkg> on Solaris 8.
|
|
|
|
rework pkg_info(8) operating on binary packages, deprecating the `-.'
argument as it is no longer required (but is retained as a no-op for
backward compatibility).
the behaviour is now what is expected and intended:
- when the pkg argument is path (absolute or relative) to a
binary pkg, pkg_info operates on it.
- when no pkg argument is given, or the argument is not a
binary pkg path, pkg_info operates on the installed packages.
`pkg_info foo-1.0.tgz', `pkg_info /path/to/foo-1.0.tgz', etc. now work
correctly when foo-1.0.tgz is in the cwd.
bump PKGTOOLS_VERSION to 20050210.
|
|
with WARNS=2 from src/usr.sbin/pkg_install. No functional change and
no version bump.
|
|
branch of src). Changes from version 20050106:
Teach pkg_add(1) and pkg_delete(1) to pass PKG_METADATA_DIR and
PKG_REFCOUNT_DBDIR in the environment when running the +* scripts.
PKG_METADATA_DIR is the location of the +* files after the package is
registered. PKG_REFCOUNT_DBDIR is the location of the reference counts
database directory. If PKG_REFCOUNT_DBDIR is left unset, then it
defaults the the location of the package database directory with
".refcount" appended to the path, e.g. /var/db/pkg.refcount.
pkgviews users should explicitly set PKG_REFCOUNT_DBDIR in the shell
environment to ensure that all packages will use the same refcount
database.
These changes allow the +INSTALL and +DEINSTALL script to keep state
in +* files within ${PKG_METADATA_DIR}, and to store reference counts
in ${PKG_REFCOUNT_DBDIR} to handle usage of resources outside of
${LOCALBASE}.
|
|
revision of src/usr.sbin/pkg_install as of 20050204. I ran:
cd pkgsrc/pkg_install/files
./pkg_install2nbcompat .
Then I ran "cvs diff" and looked for portability-related changes that
were removed as a result of the import and resurrected them from the
repository.
|
|
|