Up to [cvs.NetBSD.org] / pkgsrc / pkgtools / pkg_install / files / info
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
pkg_install-20180425: correctly detect package names in PKG_DBDIR If PKG_DBDIR is /foo and a path like /foobar is given, it is not below PKG_DBDIR, so don't translate it into a package name look up. The old logic for giving a path to PKG_DBDIR remains for legacy compat.
Update manual pages for better wording, and a better usage display for pkg_info(1) - from Bug Hunting in PR pkg/47328. The following text is taken from Bug's PR: The pkg_info(1), pkg_admin(1), and pkg_install.conf(5) man pages from pkgsrc' pkgtools/pkg_install package contain errors, have inaccurate / incomplete / illogically ordered descriptions, have incorrect macro usages / macro errors, miss an option description (`-h', for pkg_info(1)), and / or contain other imperfections. In short: these man pages can use a big correction update. Additionally, the `usage' message in main.c from pkg_info(1) contains an incorrect option order.
pkg_install-20100122:
- Refactor man pages:
- Move description of environmental variables into pkg_install.conf(5)
- Remove a bunch of dead references
- Avoid using hard-coded path names that can easily be overridden by
the user.
- Refactor pkgdb related logic, so that -K behaves consistently.
- Add some helper functions to isolate more places from the pkgdb
layout.
- Sync license list.
- Handle PKG_REFCOUNT_DBDIR consistently as option too.
- Utilize connection cache from libfetch.
- Add helper target for cat pages updates.
Update to 20100120: - Make PKG_DBDIR customizable through pkg_install.conf. Things seem to work fine after a few tests but... where are the tests for these tools?!
pkg_install-20090911: - Cleanup configure.ac to not check for headers and functions not used - Always use nbcompat/db.h on !NetBSD (PR 41865) - Don't bother setting termwidth in pkg_info, it is never used.
pkg_install-20090727: Make pkg_install WARNS=4 clean and fix a number of lint warnings. Based on reports from veego about warnings with older GCC releases in pkg_delete, where a variable is potentially used uninitialized.
G/C PlayPen and PlayPenSize.
pkg_install-20090302: Add new option -r to pkg_info, which works like -R, but expands it recursively.
pkg_install-20090228: Integrate the PKG_PATH logic for tightly with the find_archive logic: - remember initial current working directory from the time PKG_PATH is processed, it will be used as reference for all relative entries - remove now redundant fchdir dance in pkg_add - pass down to find_archive if this is a top-level package (e.g. requested on the command line) or not; the location of top-level packages is searched for packages first and for URLs or path names the PKG_PATH itself is not processed (e.g. pkg_add foo/bar not look into PKG_PATH for bar). This addresses PR 33884 in a different way. - document the rules for finding packages more explicitly - allow specifying PKG_PATH in pkg_install.conf as well; environment takes precendence. - remove PKG_PATH related logic in pkg_info(1), it doesn't deal with PKG_PATH anyway - remove PKG_PATH, PKG_TMPDIR and TMPDIR description in pkg_info(1), they are no longer used
Merge pkg_install-20090201 from pkg_install-renovation branch.
- DB support is always included from libnbcompat if needed
- pkg_view and linkfarm are not installed any more; they are not moved
into the attic yet, so they can easily be installed as separte package
- common configuration file to customise the behavior of various
components; this supersedes the old audit-packages.conf
- support for PKSC7 signatures (using X509 certs) and GPG signatures for
packages in a secure way. See pkg_admin(8) for how to create them and
pkg_install.conf(5) for the options to use them
- audit-packages and download-vulnerability-list are wrapper scripts
around pkg_admin. They try to mimic the classic options if used sanely.
"pkg_admin audit" is now an order of magnitude faster than before
- pkg_add uses libarchive and libfetch instead of external ftp and tar:
- progress bar is currently missing for downloads
- "pkg_add -" is no longer supported
- no adhoc check for conficts between dependencies and already
installed packages
- "pkg_add -s" has been replaced with an option in pkg_install.conf,
verification of plain detached GPG signatures is no longer supported
- optional check for vulnerabilities before adding a package
- if /var and /usr/pkg are on different fileystems it is twice as fast
now
- conflicts due to overlapping plists are checked before installation
- pkg_add no longer plays with the process limits
- pkg_add and pkg_delete have a new destdir option; scripts have to
either be modified to use PKG_DESTDIR or should be disabled
- pkg_add -u for now can't be used to update to the exact same version
- internal "rm -rf" and "mkdir_p" code
- all memory allocation failures are not explicitly fatal
- if a file is not removed due to a failed checksum, still remove the
entry from pkgdb
pkg_install-20090201: - sync DESCR and MESSAGE with HEAD and the branch state - sync Makefile - regen configure - cleanup __RCSID - merge audit logic in pkg_add and pkg_admin into new audit_packages function. As side effect, pkg_add will list all vulnerabilities before asking the user whether it should continue - sort config_variable array
Most memory allocation failures were fatal already and the majority of the rest lacked an explicit check. Add the usual x* wrappers around malloc and friends that explicitly terminate on error and use them in all but Dewey.
Also add -E to usage(). From PR 37265.
Remove obsolete option r from usage() and man page. I can't even remember what is was for. From Yakovetsky Vlad in PR 37265.
Make _pkgdb_getPKGDB_DIR return const char * and fix fallout.
pkg_admin: when retrying with a wildcard pattern, use the computed pattern and not the base name. pkg_info: add -E option to return the best matching installed package. Bump to 20070813.
Replace note_whats_installed, add_to_list_fn and generally most users of findbestmatchingname and findmatching name with more descriptive and easier to use iterator functions. This functions are a first step to abstract away pkgdb layout from most parts of the code. It also helps to reduce side effects and point out potential bugs in this code. Fix a potential, but practically irrelevant buffer overflow. No longer allow symbolic links directly in pkgdb to store the meta data of individual packages outside. E.g. /var/db/pkg/atk-1.18.0 must be a directory and not point to it. This is not yet enforced in all parts of the code, more changes will follow. Bump version to 20070808.
After the obsoletion on March, remove the support for require scripts. Also remove the documentation of the mtree parts as it is not supported.
Update usage() - sync with manpage, add missing options, etc.
Sync with src, version 20060424: Add support for creating summary file containing all information about a package repository needed by package managing software. This allows better use of remote binary package repositories. Discussed on tech-pkg.
Sync with base system as of Sat Nov 5 13:19:32 UTC 2005. Welcome to 20051103! Now with "automatic" support.
pull in binary pkg handling changes from src:
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.
Pull in portability changes from src, and bump version to 20041226: Introduce a new abstraction in the C code, called MaxPathSize. All 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.
Update pkgtools/pkg_install to 20040813 (latest release from the HEAD
branch of src). Changes from version 20040730 include:
Modify pkg_info so that it will only print information on uninstalled
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 (agc), which completely
violated the POLS.
Add a -q switch to pkg_admin, which allows it to work in a quiet
manner. Fixes the change request in PR 26583, but in a different
manner, preserving existing behaviour and making the new behaviour
dependent upon a command line option.
Import pkg_install-20040508. Fixes the -N flag to not cause the -Q codepath to be executed by correcting the SHOW_* macro definitions. Also fix up some function prototypes so this builds with -Wall. Fixes from pkg/25494.
Import pkg_install-20040507 from src/usr.sbin/pkg_install: Add a new flag -Q (for "query") to pkg_info(1) to query the build 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
1.39 from usr.sbin/pkg_install/info/main.c: Check pkgdb_open for correct return value. From Peter Postma in PR 24863.
pkg_install now prints post-install message by default, if available.
sync with NetBSD-current's pkg_install-20030923.
Sync to latest pkg_install sources from the HEAD for pkg_delete optimizations and man page fixes. Also use recent src2nbcompat to reverse the order that "config.h" and <nbcompat.h> are included in *.[ch] files.
Update pkg_install to 20030823, which has the changes to support package views. Pkgsrc changes include: * Convert to use pkgtools/libnbcompat so that it's easier to keep this in sync with src/usr.sbin/pkg_install. * Add a src2nbcompat script that converts src/usr.sbin/pkg_install into an appropriate start for pkgtools/pkg_install. The script removes the Makefiles, adds CPP inclusion guards around each #include <...> line, and includes <nbcompat.h> at the top of each *.c file. This should make it even easier to keep sources in sync with the HEAD.
Synch with main sources: Changes by hubertf and seb; these changes tested on NetBSD, Linux and Irix. Modified Files: src/usr.sbin/pkg_install/add: perform.c pkg_add.1 Log Message: Implement remaining TODO item in pkg upgrade (pkg_add -u): * Upgrade step 1/4: Check if the new version is ok with all pkgs * (from +REQUIRED_BY) that require this pkg Inspired by bsd.pkg.mk's upgrade(?) target. Modified Files: src/usr.sbin/pkg_install/admin: main.c src/usr.sbin/pkg_install/info: main.c perform.c Log Message: Consistently check findmatchingname() return value for error condition. Among other this fixes 'pkg_info -e whateverpkg' exit status when /var/db/pkg is missing: it is now 1 and not 0. Modified Files: src/usr.sbin/pkg_install/lib: version.h Log Message: Bump to "20030325" after today's changes from seb and me
Synch with basesrc: Use EXIT_FAILURE, rather than hardcoding a value of '1' in err(3) and errx(3). Plug a memory leak by modifying the signature of _pkgdb_getPKGDB_FILE() to take a buffer and its size, and fill in that buffer and return it. Add an enumerated type which is used in pkgdb_open() to specify read-only or read-write mode. Modify the return value of pkgdb_open() to have a more logical boolean value.
Import autoconf'd pkg_install source from
othersrc/bootstrap-pkgsrc/pkg_install into ${FILESDIR}.
Using autoconf greatly simplifies maintenance of this package across
multiple platforms. Placing the extracted source under ${FILESDIR}
will eventually let us use the same source for bootstrapping as
well, though we're not ready for this yet.
Initial revision