that has been in pkglint before I started hacking it. Mostly, they don't
contain a specific file location where to look for the cause or they are
generated using dubious code. The remaining warnings are only a few, but
they are mostly usable and valid.
Replace ${PHPPKGSRCDIR} with ../../lang/php5 when expanding Makefile
variables. Show a warning if Makefile variables contain unresolved
substitutions after expanding them. Fixed a newly introduced bug that
prevented bsd.sites.mk from being found.
around at either build-time or at run-time is:
USE_TOOLS+= perl # build-time
USE_TOOLS+= perl:run # run-time
Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.
run-time dependency (DEPENDS) on a tool is to append a ":run" modifier
to the tool name, e.g.,
USE_TOOLS+= perl:run
Tools without modifiers or with an explicit ":build" modifier will
cause build dependencies (BUILD_DEPENDS) on those tools to be added.
This makes the notation a bit more compact.
This is the first step to get rid of the global $opt_packagedir
variable. While doing this, I will hopefully notice all uses of relative
pathnames and repair them, so that pkglint can be called with multiple
arguments soon.
therefore renamed it to -Wplist-sort. This option is disabled by default
to avoid excessive warnings. Apart from an unfounded suggestion
somewhere in the past, I don't see a reason why PLIST files should be
sorted. Remember: The option is still available, it's just disabled by
default.
rather than just pretending to. I know I meant this to work, but
somehow I forgot actually to make it work a long time ago.
Addresses a problem pointed out in private email.
updates. Don't write logging messages for Makefiles that are being read
but for Makefiles that are included and for those whose inclusion is
skipped. Skip include files that contain Make variables. When checking
for direct use of shell commands, don't print the line continuation,
that is the trailing white-space and backslash. These changes lead to
pkglint-4.18.
the make required by the imake config files, which is specified by
${IMAKE_MAKE}. This allows differing make programs to be used for
the main build versus xmkmf.
invoking the make(1) program as "make" instead of hardcoding the
(wrong) path in ${MAKE_PROGRAM}. This will rely on the tools framework
to have set up "make" to properly call the correct make(1) program.
This should fix cases where pkgxmkmf called the wrong make(1) program
on Linux systems.
- Make the EXTRA_MK variable be a list of files rather a single one.
From brook at biology.nmsu.edu in PR pkg/30099.
- Directly recognize pkg_* commands to be executed within the sandbox
(i.e., no need to use the chroot keyword).
From Robert Elz in PR pkg/29749.
- Fix a typo in the manual page.
the files in the work directory are built to discover the directories
that need to be removed at deinstall time. This fixes PR pkg/25325 by
Georg Schwarz.
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
- sort -l output so that dependencies always come before packages
which depend upon them
- completely rework -u so that a list of packages to be update is generated,
then all mismatched packages are removed, then the list is processed to
add in packages. If -u is interrupted, a second run will resume the update
- update (-u) works with binary packages
beginning of a line. This fixes false warnings for variables that are
commented out. Added ${JAM_COMMAND} to the commands that may have
"install" or "test" as arguments.
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.
checks. Currently the effects are that buildlink3.mk files are read in.
Moved around code in checklines_direct_tools to allow $regex_tools to be
used in the list of legitimate shell commands. Added a new rule that
legitimates tool names inside double quotes.
scanning package Makefiles. Changed the output format to include a
newline where necessary. Added the search path to the error message.
This might fix PR 30322.
commands. The warnings are precise (file, line, varname, shellcmd) and
can be easily translated into Perl code. They might even be placed in
external files someday.
complete Makefile with includes and a list of lines, also with includes.
This list of lines is the first step towards better error and warning
messages (including file and line number). A first effect of this change
is that the use of Makefile variables is checked even in the .include'd
Makefiles.
numbers to the warnings and allows to check for trailing empty lines in
patch files. Embedded the check for files not ending with newlines into
the load_file() subroutine.
results in much less false warnings, but sadly adds some to the
koffice-18n packages. The main reason for this change is that the
execution time of pkglint is reduced by 20%.
Two fixes to -l (list required binary packages to stdout)
a) If a dependency is missing, display its name correctly
b) Display any progress to stderr not stdout (for obvious reasons)
This package installs a script called genrpm, which is used to
generate a Redhat Package Manager (RPM) package from an installed
pkgsrc package. It does this by generating a spec file, and using
that to identify the components of the RPM and package them.
If a pkgsrc tree is present on the system, a source RPM (or srpm)
can also be generated. This will include the distfile, any pkgsrc
patches, and the files used to accomplish the pkgsrc packaging.
seems to be really useful now, and it's ready to be on pkgsrc).
pkg_select will display a curses file browser for the pkg system. You can
browse pkgsrc and gather various informations about packages, like avail-
able version, installed version, comment and homepage. A simple paging
system lets you read information files. You can browse both installed
and uninstalled packages, as well as dependencies list and perform vari-
ous administrative tasks to them. A package finder system helps you to
easily locate a package by its name. pkg_select can handle either source
or binary installations when pkgsrc is installed on the local system, or
binary only when using the pkgsrc-over-ftp feature.
If no pkgsrc is installed, pkg_select offers ability fo fetch it, either
by FTP or CVS. It is also possible to update an existing pkgsrc via the
interface.
pkg_select user interface is quite self explainatory, every available
shortcut is shown and annotated.
added in this version, taken from the reference code from the NESSIE
project. Passes regression test suite on NetBSD/{i386,sparc64} and
also on SunOS 5.9 sparc (thanks, Jonathan).
* 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
which have no extutil.h header file, just make them depend on the
xextensions package which provides it.
Bump PKGREVISION for Xrandr and randrext.
Add builtin.mk file for xextensions.
jlam says ok.
Add new -N option, showing for each installed package any corresponding
entries in pkgsrc/doc/TODO (to give you an idea what updates you could
be interested in :) ).
While here, sort options in usage.
Ok'd by abs@.
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.
