Replace @VAR@ with ${VAR} unconditionally in scripts, even if they
values are empty. This will allow for fall-through to using the
pkgtasks hard-coded defaults, usually found by searching the PATH
contents, and it avoids having ugly "@VAR@" in the generated
scripts.
These changes aren't necessary, but on the day when guile-2.0.x is
no longer the primary, then the switch to using a non-default
installation prefix should be seamless.
If Guile installs into a non-default installation prefix, then
use ${GUILE_PREFIX}/info and ${GUILE_PREFIX}/man as the locations
for the installed GNU info files and manpages. This avoids needing
to do a lot of fixes to the PLISTs.
This project uses CMake to configure the software. Force the GNU
info files to be installed into ${CMAKE_INSTALL_INFODIR}, which is
defined by the GNUInstallDirs CMake module included by the
top-level CMakeLists.txt file. The corrct environment variables
are passed so that ${CMAKE_INSTALL_INFODIR} points into
${PKGINFODIR}.
Remove the subst.mk section that tried to force GNU info files to
be always installed under "info".
Complete the support for installing manpages into ${PKGMANDIR}
that was previously started -- also copy the manpage into the
correct directory under ${PKGMANDIR}.
Override MANDIR=man settings in project Makefiles by passing an
explicit MANDIR=${PKGMANDIR} on the make(1) command line so that
manpages are installed into the correct location under
${PKGMANDIR}.
This project uses CMake to configure the software. Force the
manpages to be installed into ${CMAKE_INSTALL_MANDIR}, which is
defined by the included GNUInstallDirs CMake module. The correct
environment variables are passed so that ${CMAKE_INSTALL_MANDIR}
points into ${PKGMANDIR}.
Set MANDIR in Makefile.inc to point to ${PKGMANDIR} so that
the BSD makefiles that include Makefile.inc will install manpages
into the correct location.
This project uses BSD makefiles to build and install the binaries
and manpages. Add "MANDIR=..." to the flags passed to
"make install" so that the manpages are installed in the correct
location under ${PKGMANDIR}.
This package uses CMake to configure the software. Include the
GNUInstallDirs CMake module to define CMAKE_INSTALL_<dir> macros,
and use CMAKE_INSTALL_MANDIR as the location for the installed
manpages. The correct environment variables are passed so that
${CMAKE_INSTALL_MANDIR} points into ${PKGMANDIR}.
Modify the Makefile patch to properly install manpages under
${PKGMANDIR}. The previous rules were inconsistent -- some places
referred to "man/" and others to "${PKGMANDIR}/".
This package uses a custom "do-install" target to install all of
the package's files. Change the command to install the manpage to
put it under ${PKGMANDIR}.
This project uses a Perl-style Configure script that can use a
custom config.sh to provide default answers to questions that it
asks as part of the configuration process. Modify the custom
${FILESDIR}/config.sh to allow substituting for @PKGMANDIR@ in the
default location for unformatted manpages.
This project uses BSD makefiles to build and install the binaries
and manpages. Add "MANDIR=..." to the flags passed to
"make install" so that the manpages are installed in the correct
location under ${PKGMANDIR}.
Patch the project Makefile to honor @mandir@ which is substituted
for by the GNU configure script. @mandir@ will properly expand
to point inside ${PKGMANDIR}.
This package uses CMake to configure the software. Include the
GNUInstallDirs CMake module to define CMAKE_INSTALL_<dir> macros,
and use CMAKE_INSTALL_MANDIR as the location for the installed
manpages. The correct environment variables are passed so that
${CMAKE_INSTALL_MANDIR} points into ${PKGMANDIR}.
- Command history based on readline.
- New commands: coords/nocoords to enable/disable coordinates
when printing the board.
- Command pgnsave will prompt the user to overwrite or not an existing
file instead of appending the current game to the file.
- New languages.
- Bug fixes.
- Corrected so-name version
release 4.11:
- Introduced the ASN1_TIME_ENCODING_ERROR error code to indicate
an invalid encoding in the DER time fields.
- Introduced flag ASN1_DECODE_FLAG_ALLOW_INCORRECT_TIME. This flag
allows decoding errors in time fields even when in strict DER mode.
That is introduced in order to allow toleration of invalid times in
X.509 certificates (which are common) even though strict DER adherence
is enforced in other fields.
- Added safety check in asn1_find_node(). That prevents a crash
when a very long variable name is provided by the developer.
Note that this to be exploited requires controlling the ASN.1
definitions used by the developer, i.e., the 'name' parameter of
asn1_write_value() or asn1_read_value(). The library is
not designed to protect against malicious manipulation of the
developer assigned variable names.
