pkglint --only "https instead of http" -r -F
With manual adjustments afterwards since pkglint 19.4.4 fixed a few
indentations in unrelated lines.
This mainly affects projects hosted at SourceForce, as well as
freedesktop.org, CTAN and GNU.
Problems found with existing distfiles:
distfiles/fvwm-1.24r.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.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
since they always need a C compiler, even when the source code is
completely in C++.
For some other packages, stated in the comment that a C compiler is
really not needed.
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.
- pulling patch in from David Dellanave (solaris compile issues)
- fixing compilation issue for Mac OS X (thanks to Thomas F. Burdick!!)
- fixing bug in token-parsing (thanks to Adam Hooper!!!)--we now allow
")"'s in our ExecCommands.
- fix recursive redhat-build bug (fixes 577135)
- fix a memory leak in ToolWindow::windowAttributeChange.
- remove server grabs from the Image code. They prove to not be needed (they
no longer exist in the blackbox code.) And they cause the X server to lock
indefinately if you run 2 bbkeys on the same display, running the second
one from a terminal on the display.
- when we recieve a startup message from blackbox, clear out any leftover
windows in the window list. These are caused by the fact that on shutdown
of blackbox, if any windows are unmanaged after bbkeys, bbkeys doesn't get
notified of their destruction and so ends up with extra windows in its list.
- fix compiling issues under solaris. Thanks to grub on irc for use of his
time for testing.
- get rid of work-around for pre-0.60 blackbox, which fixes bug that let you
move the toolbar around with bbkeys.
- fix window focus tracking bug. Fixes bug where you could manipulate the
last focused window on a nono-visible workspace.
- fix multi-head bug in main.cc. We now putenv("DISPLAY=...") so that
applications launched will be launched on the correct display. Thanks to
Greg Gilbert for his patch!
- fix bug in main.cc (| rather than ||). Thanks to Roman Neuhauser!
- fix bug in bbkeys.hh--increasing MaxInstructions to 100 for cthulhain
- fix in bbkeys.cc -- XUngrabKey changed to use same call to find what
screen we're on as the XGrabKey call
- fix in bbkeys.cc -- doing "xterm -e sh -c $command" rather than "xterm -e
$command". Thanks to Magnus Solvang for the bug report. Also, changing
hideous char* and snprintf() to ostrstream, YAY!!
to ${X11BASE} in the header and library search paths into references to
${LOCALBASE}/share/x11-links. These packages should now be strongly-
buildlinked regardless of whether xpkgwedge is installed.
Changes well-tested on NetBSD-1.5X/i386 with and without xpkgwedge and
lightly-tested on NetBSD-1.5.1/alpha without xpkgwedge.
Provide keyboard shortcuts for X11R6, specifically intended for use with
the Blackbox window manager but usable with any.
Can bind actions such as executing commands, altering the states of windows,
switching workspaces, etc. to arbitrary keys.
Note: since the basic package does not install the qt-based configuration
tool, bbkeys ought to be invoked with the -noqt option unless you also
install the wm/bbkeys-qt package.
Submitted by Al Snell <alaric@alaric-snell.com> in PR 11259
