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.
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}.
Bump the pkg_install version to 20050204.
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.
package to make pkg_add work properly when no +BUILD_INFO file exists.
Modify the return value from read_buildinfo() to return 1 for success
and 0 for failure.
Use symbolic constants, rather than integers.
If we can't read the build information, always tell of this fact.
Bump version to 20040730
Addresses PR 26429; a different version of these mods were verified to
allow a +BUILD_INFO-less binary package to be added by Martin Husemann.
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.
(IGNORE_RECOMMENDED set in the presence of RECOMMENDED pre-requisites).
This change is fully backward-compatible: binary packages have set the
corresponding BUILD_INFO since RECOMMENDED was implemented. Packages
built before that time will install as before.
Bump PKGTOOLS_VERSION to 20040411.
This closes PR pkg/24712 by Thomas Klausner.
are installed as part of the package.
Enable the verification of the integrity of any symbolic links
in the package in "pkg_admin check".
Add a check to pkg_delete to verify the integrity of the symbolic link
before deletion, and to act in the same way as an MD5 failure if the
symbolic link has been modified since package creation time.
Bump version number.
Addresses PR 23048 from Klaus Klein.
the former represents the CPU architecture, which is what is recorded
in binary packages.
also allow the OS name to be overridden, as pkgsrc doesn't always use
the value of utsname.sysname.
bump version to 20030113.
bpm uses ftp(1) and pkg_add(1) to allow a menu-based addition of
binary packages from a URL. It first displays a list of categories,
and, within categories, binary packages, which can be added to the
local system simply by choosing them from a menu.
If no valid categories are found, a warning message will be displayed
(it is usually caused by people running NetBSD-current, and there are
rarely binary packages provided for such a fast-moving target, and the
"-r release" command-line switch to bpm(1) should be used).
Bump the pkg_install version number for this.
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.
and spit out a warning if any of them differ. bail if the OS or arch
differ. installation can be forced with -f.
sanity checked by simonb. fixes PR pkg/18966 from mrg.
