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().
Use this in pkg_add to mark installed dependencies as automatically installed.
pkg_add: new flag -A: marks package as automatically installed.
pkg_admin: new commands set and unset to modify variable pairs for
installed packages.
pkg_info: report these variable pairs with -Q/-B.
new flag -u: report only manually installed packages (not
installed with pkg_add -A).
Error out if -a/-u and a package name is specified.
Joint work with Thomas Klausner.
As discussed on tech-pkg.
display the package name with every warning message when displaying the
contents of metadata files.
Whilst I'm here, correct the function name in another warning message.
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.
previous occurrences of MAXPATHLEN and FILENAME_MAX have been changed
to use MaxPathSize instead.
If MAXPATHLEN is not defined, then assume a default value of 1024
(this is primarily for use on the Hurd).
The reason for this is that some older platforms define FILENAME_MAX
to be 14, although MAXPATHLEN is 1024. On BSD-derived systems,
FILENAME_MAX And MAXPATHLEN are both 1024.
Bump pkg_install version to 20041226.
These modifications have been tested so far on a NetBSD-current bulk
build.
binary packages in the current working directory if -. is given on the
command line. If no -. is given, pkg_info will look for its information
in the ${PKG_DBDIR}.
This addresses a long-held gripe on the part of a number of people,
including myself, which completely violated the POLS.
Bump version for this and previous pkg_admin modification.
have all the files from ALL_FNAMES -- meta pkgs don't have +MTREE-files,
and as such it's impossible to retrieve _any_ information on them.
The fix is to only extract those +-files that are needed (as determined
by the command line options).
Problem noted by gavan@, code reviewed by grant@ and gavan@.
information for the definitions of specific variables that were saved
from build time, e.g.
$ pkg_info -Q PKGPATH glib
devel/glib
$ pkg_info -Q PROVIDES glib
/usr/pkg/lib/libglib.so.13
/usr/pkg/lib/libgmodule.so.13
/usr/pkg/lib/libgthread.so.13
Bump the version number of pkg_install(1) to 20040507.
and gdk-pixbuf-gnome-0.22.0nb1, so make sure that lines don't wrap.
Instead of having maxline based on MAXNAMESIZE, have it be based
on the length of the package name if longer than MAXNAMESIZE.
(This was discussed on tech-pkg list in November, 2003.)
the file descriptor handling mess in lib/file.c.
also use --fast-read where applicable.
result of pkg_info -B on 1.5ghz pentium4, linux:
before after
mozilla-1.4nb1.tgz 1.96sec 0.04sec
mozilla-1.4nb1.tbz 18.66sec 0.21sec
866mhz pentium3, NetBSD:
before after
mozilla-1.4nb1.tgz 2.22sec 0.07sec
mozilla-1.4nb1.tbz 16.29sec 0.34sec
-rw-r--r-- 1 grant users 13816195 Dec 20 13:59 mozilla-1.4nb1.tbz
-rw-r--r-- 1 grant users 15814227 Dec 20 13:58 mozilla-1.4nb1.tgz
XXX fetches over ftp/http still read the whole file.
Add the ability to pkg_info(1) and pkg_delete(1) to take a directory
name for the name of the package, so that shell-completion can help
when finding out information or deleting packages.
