Unsorted entries in PLIST files have generated a pkglint warning for at
least 12 years. Somewhat more recently, pkglint has learned to sort
PLIST files automatically. Since pkglint 5.4.23, the sorting is only
done in obvious, simple cases. These have been applied by running:
pkglint -Cnone,PLIST -Wnone,plist-sort -r -F
Problems found with existing digests:
Package memconf distfile memconf-2.16/memconf.gz
b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
95748686a5ad8144232f4d4abc9bf052721a196f [calculated]
Problems found locating distfiles:
Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
Its signature is changed at libpcap-1.0, not DragonFly specific,
and it should be defined by include of pcap.h, no need to define here.
fixes PR#45035.
* In order for pftop to be built successfully with newer PF
versions (> 4.1), additional patches are necessary which were taken
from OpenBSD's ports as seen in PR pkg/44339
* Pftop compiled for another PF version will not work (properly),
so to avoid any problems we must depend on the OS version
ok@ wiz
Changes in version 0.7:
This version adds state filtering, which is funded by backcountry.com,
many thanks. It is now possible to select which states are displayed
using a tcpdump(8) like filtering language. The filter can be specified
on the command line, using the '-f' switch. It is also possible to
change the filter interactively using the 'f' command key.
Some sample, not necessarily practical, filters are given below:
- Do not show pfsync or carp traffic:
not (pfsync or carp)
not pfsync and not carp
- DNS traffic not going to or coming from the DNS servers:
port 53 and not host (10.0.0.10 or 10.0.0.11)
- States with input bytes greater than 1M:
inb > 1000000
- Traffic with very small average packet size:
((inb / inp) + (outb / outp))/2 < 100
inb / inp + outb / outp < 200
Changes in version 0.6:
No functional changes. It now compiles and runs on OpenBSD 4.1-current
after pf interface changes. This version also contains separated pf
and display code. This should make adding new views easier.
Changes in version 0.5:
This version displays all active pf rules by traversing the ruleset tree.
In addition HFSC queues are now displayed correctly thanks to
Jared Spiegel. This version also incorporates other patches and comments
I have received since the previous release. Many thanks to all who have
contributed.
- New command-line switch 'S' to start the display at a given state.
- Display HFCS statistics in the queue page.
- Fixed state and rule byte and packet counters
- Fixed state sorting by packets and bytes
- Fixed some minor display problems
- The rule view now traverses all rulesets, and displays all active rules,
together with anchor (ruleset) names.
- Anchor and Label fields dynamically resize themselves
INSTALLATION_DIRS, as well as all occurrences of ${PREFIX}/man with
${PREFIX}/${PKGMANDIR}.
Fixes PR 35265, although I did not use the patch provided therein.
NetBSD 2 + pflkm, because the path was substituted by "__nonexistent__".
So to fix this properly, add a patch with CPP conditional which fixes
the path for __DragonFly__.
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.
