libidn-1.33: registering info file /usr/pkg/info/libidn-components.png
libidn-1.33: registering info file /usr/pkg/info/libidn.info
libpaper-1.1.24: copying /usr/pkg/share/examples/libpaper/papersize to /usr/pkg/etc/papersize
libffi-3.2.1nb2: registering info file /usr/pkg/info/libffi.info
No schema files found: doing nothing.
xmlcatmgr-2.2nb1: copying /usr/pkg/share/examples/xmlcatmgr/catalog.etc.sgml to /usr/pkg/etc/sgml/catalog
xmlcatmgr-2.2nb1: copying /usr/pkg/share/examples/xmlcatmgr/catalog.etc.xml to /usr/pkg/etc/xml/catalog
xmlcatmgr-2.2nb1: copying /usr/pkg/share/examples/xmlcatmgr/catalog.share.sgml to /usr/pkg/share/sgml/catalog
xmlcatmgr-2.2nb1: copying /usr/pkg/share/examples/xmlcatmgr/catalog.share.xml to /usr/pkg/share/xml/catalog
pkg_add: package `python27-2.7.13nb1' was already installed as dependency, now marked as installed manually
dbus-1.10.16: Creating group ``dbus''
dbus-1.10.16: Creating user ``dbus''
useradd: Warning: home directory `/var/run/dbus' doesn't exist, and -m was not specified
dbus-1.10.16: setting permissions on /usr/pkg/libexec/dbus-daemon-launch-helper (o=root, g=dbus, m=4511)
===========================================================================
The following files should be created for dbus-1.10.16:
/etc/rc.d/dbus (m=0755)
[/usr/pkg/share/examples/rc.d/dbus]
===========================================================================
fftw-3.3.6pl1: registering info file /usr/pkg/info/fftw3.info
gsl-2.3: registering info file /usr/pkg/info/gsl-ref.info
pkg_add: package `gnuradio-core-3.7.10.1' was already installed as dependency, now marked as installed manually
libIDL-0.8.14nb4: registering info file /usr/pkg/info/libIDL2.info
GConf-2.32.4nb11: copying /usr/pkg/share/examples/GConf/path to /usr/pkg/etc/gconf/2/path
===========================================================================
$NetBSD: MESSAGE,v 1.1 2014/04/26 13:52:00 wiz Exp $
To customize cidfmap, copy
/usr/pkg/share/ghostscript/9.06nb9/Resource/Init/cidfmap.dist
to
/usr/pkg/share/ghostscript/9.06nb9/Resource/Init/cidfmap
and modify it.
Please consider installing another companion package
fonts/ghostscript-cidfonts-ryumin for above purpose.
Please note that the above statement only applies when the option
disable-compile-inits selected while build time. Otherwise you may
set GS_LIB environment variable to give search path for setup files.
===========================================================================
===========================================================================
$NetBSD: MESSAGE,v 1.5 2014/08/10 10:47:42 wiz Exp $
Execute this command to extract and rehash all CA root certificates
distributed by the Mozilla Project, so that they can be used by third
party applications using OpenSSL. It also creates a single file
certificate bundle in PEM format which can be used by applications using
GnuTLS.
# mozilla-rootcerts install
To mark these certificates as trusted for users of gnupg2, do
the following (assuming default PKG_SYSCONFBASE and a Bourne shell):
# mkdir -p /usr/pkg/etc/gnupg
# cd /usr/pkg/etc/gnupg
# for c in /etc/openssl/certs/*.pem; do
> openssl x509 -in $c -noout -fingerprint|sed 's|^.*=\(.*\)|\1 S|'
> done > trustlist.txt
===========================================================================
===========================================================================
$NetBSD: MESSAGE,v 1.5 2004/01/23 17:12:16 jmmv Exp $
The following catalogs have been installed:
* /usr/pkg/etc/sgml/catalog
System wide SGML catalog. Can be edited by the administrator and
is not changed by packages. This is the *default* catalog when
working in SGML mode.
* /usr/pkg/etc/xml/catalog
System wide XML catalog. Can be edited by the administrator and
is not changed by packages. This is the *default* catalog when
working in XML mode.
* /usr/pkg/share/sgml/catalog
Handles SGML stuff installed under /usr/pkg/share/sgml.
Automatically handled by packages.
* /usr/pkg/share/xml/catalog
Handles XML stuff installed under /usr/pkg/share/xml.
Automatically handled by packages.
===========================================================================
===========================================================================
$NetBSD: MESSAGE,v 1.2 2014/12/02 05:20:24 snj Exp $
You should enable the dbus system-wide daemon for correct operation. You
can do this by using one of the three start-up scripts installed by the
package. Use:
* /usr/pkg/share/examples/rc.d/dbus:
if you are using NetBSD's and pkgsrc's rc.subr start-up framework.
* /usr/pkg/share/examples/rc.d/messagebus.redhat:
if you are using a Red-Hat based system (such as Fedora).
* /usr/pkg/share/examples/rc.d/rc.messagebus.slackware:
if you are using a Slackware-like system.
===========================================================================
===========================================================================
$NetBSD: MESSAGE,v 1.1.1.1 2006/02/20 12:08:11 adam Exp $
To allow this package to coexist with other versions of Qt
it has been installed in /usr/pkg/qt4/{bin,include,lib,doc}.
You should be able to select this version of Qt when compiling
programs which use it by ensuring that
1) QTDIR is set to /usr/pkg/qt4
2) Use the "configure" argument "--with-qt-dir=/usr/pkg/qt4"
3) you may also have to put /usr/pkg/qt4/bin in your PATH
To access Qt-4 man pages add /usr/pkg/qt4/doc/man to your MANPATH
environment variable. Note that the Qt-4 man pages are installed
here to avoid conflicts with man pages of other Qt versions.
===========================================================================
===========================================================================
$NetBSD: MESSAGE,v 1.1 2008/07/31 03:58:05 bjs Exp $
NOTE: Unfortunately, JACK wants to use a linux /proc filesystem to
perform shared memory housekeeping tasks. Therefore, if your platform
supports a "Linux-compliant" proc filesystem, we recommend mounting one
prior to using jack. On NetBSD, this can be accomplished with the
following command:
mount_procfs -orw,linux /proc <mount point>
Conventionally, the mount point is /proc. If you wish to use a different
pathname for this filesystem, you may define the JACKD_PROCFS_PATH
variable in your build environment or mk.conf as shown below.
JACKD_PROCFS_PATH= /emul/linux/proc
ATTENTION: NetBSD-current users who wish to run jackd with real-time
scheduling will likely find that the loader fails to mmap
the driver module(s) when using -R. Until this issue is re-
solved, one may work around this problem by using the -m
(--no-mlock) option.
===========================================================================