everything except Makefiles. (Makefiles which will follow soon.) This makes
most warnings more useful. Together with the last few changes, we are
now at version 4.06. Approved by wiz.
messages are formatted nicer. It produces more (reasonable) warnings,
but also some more false positives. Did not increase DISTNAME, as the
change is not yet big enough. Approved by wiz.
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.
Standardize the prefix so they can be compared with the packages
more easily (pkg_chk is better at this anyway, but since I fixed
the other cases already...).
Welcome to 4.00!
Fix lintpkgsrc handling of python and ruby packages.
Remove invalid-dewey test that broke more things than it helped.
Add support for "pre" in version strings. Update comment about
recognised strings.
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.
- Add support to explicitly select which wrappers are wanted on a system and
which ones are not. This is done through a configuration file that defines
a filter with a set of actions and regular expressions (example file
included).
- Add an examples section to the manual page with solutions for some FAQs.
- Substitute default values for GREP, PKG_INFO, and SED at buildtime
- Add -P dir, to set binary package dir
- Remove the need for a copy of pkgsrc when using -b
- List 'missing' packages at the end alog wwith Installed and Failed
- Output various messages to stdout and to logfile (if active)
- As ever, there are few problems that cannot be helped by
adding another layer of abstraction
- get rid of asprintf
- use libnbcompat if necessary
- while here, get rid of unused variable
Bump date.
ok peter@, tv@
Non-NetBSD platforms may need to test this and adjust following the IRIX
example.
- Add the destroy action, used to remove the alternatives database as well
as any known wrappers.
- Use the rebuild/destroy actions at install/deinstall time respectively
so that this package can be installed at any time and pick up automatically
available alternatives from PKG_DBDIR.
Per suggestion from reed@ in tech-pkg@.
pkg_alternatives is a tool to manage the alternatives system provided by
The NetBSD Packages Collection, also known as pkgsrc. It creates, configures
and destroys generic wrappers used to run programs with similar interfaces.
No objections in tech-pkg@. Agreed with jlam@, who has provided lots of
design suggestions.
