initial sweep for MESSAGE decoration removal; ok espie@
This commit is contained in:
danh
parent
2ce59a4b18
commit
6362fb0bc7
@ -1,6 +1,4 @@
|
||||
+---------------
|
||||
| Now, you might want to install one of the following players;
|
||||
| audio/mpg123 audio/mpg321 audio/madplay audio/xmp audio/sox
|
||||
|
|
||||
| If you intend to do anything useful with cplay, that is.
|
||||
+---------------
|
||||
Now, you might want to install one of the following players;
|
||||
audio/mpg123 audio/mpg321 audio/madplay audio/xmp audio/sox
|
||||
|
||||
If you intend to do anything useful with cplay, that is.
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
+-----------------------------------------------------+
|
||||
| Gqmpeg has been installed as a front-end to mpg321. |
|
||||
| However you can additionally install other players |
|
||||
| such as xmp, mpg123 and ogg123. These are supported |
|
||||
| by Gqmpeg. |
|
||||
+-----------------------------------------------------+
|
||||
Gqmpeg has been installed as a front-end to mpg321.
|
||||
However you can additionally install other players
|
||||
such as xmp, mpg123 and ogg123. These are supported
|
||||
by Gqmpeg.
|
||||
|
||||
@ -1,4 +1,2 @@
|
||||
+-----
|
||||
| To use mp3cddb please consult readme.txt installed in
|
||||
| ${PREFIX}/share/doc/mp3cddb
|
||||
+-----
|
||||
To use mp3cddb please consult readme.txt installed in
|
||||
${PREFIX}/share/doc/mp3cddb
|
||||
|
||||
@ -1,10 +1,6 @@
|
||||
+----------------------
|
||||
|
|
||||
| Before the normalize-mp3 and normalize-ogg scripts can be
|
||||
| used, you first need to install mpg321 and lame for normalize-mp3,
|
||||
| add vorbis-tools for normalize-ogg.
|
||||
|
|
||||
| These extra packages are not required for normal operation of
|
||||
| normalize.
|
||||
|
|
||||
+----------------------
|
||||
Before the normalize-mp3 and normalize-ogg scripts can be
|
||||
used, you first need to install mpg321 and lame for normalize-mp3,
|
||||
add vorbis-tools for normalize-ogg.
|
||||
|
||||
These extra packages are not required for normal operation of
|
||||
normalize.
|
||||
|
||||
@ -1,8 +1,4 @@
|
||||
+------------------------------------
|
||||
|
|
||||
| The README has been installed in
|
||||
| ${PREFIX}/share/doc/tempest/README
|
||||
| Please read it prior operating this
|
||||
| software.
|
||||
|
|
||||
+------------------------------------
|
||||
The README has been installed in
|
||||
${PREFIX}/share/doc/tempest/README
|
||||
Please read it prior operating this
|
||||
software.
|
||||
|
||||
@ -1,13 +1,11 @@
|
||||
+---------------
|
||||
| Before using xmcd/cda for the first time, you must
|
||||
| set up the software by running the following program:
|
||||
|
|
||||
| $PREFIX/sbin/xmcdconfig
|
||||
|
|
||||
| Xmcd/cda will not work until that is done.
|
||||
|
|
||||
| You may also want to set up cron(8) to run the
|
||||
| $PREFIX/share/xmcd/scripts/genidx script periodically
|
||||
| (e.g., nightly) to re-generate the local discography
|
||||
| category index pages.
|
||||
+---------------
|
||||
Before using xmcd/cda for the first time, you must
|
||||
set up the software by running the following program:
|
||||
|
||||
$PREFIX/sbin/xmcdconfig
|
||||
|
||||
Xmcd/cda will not work until that is done.
|
||||
|
||||
You may also want to set up cron(8) to run the
|
||||
$PREFIX/share/xmcd/scripts/genidx script periodically
|
||||
(e.g., nightly) to re-generate the local discography
|
||||
category index pages.
|
||||
|
||||
@ -1,7 +1,5 @@
|
||||
+---------------
|
||||
| To run xcin25, you have to set the following environment
|
||||
| variables in csh or tcsh:
|
||||
|
|
||||
| setenv LC_CTYPE zh_TW.Big5
|
||||
| setenv XMODIFIERS "@im=xcin"
|
||||
+---------------
|
||||
To run xcin25, you have to set the following environment
|
||||
variables in csh or tcsh:
|
||||
|
||||
setenv LC_CTYPE zh_TW.Big5
|
||||
setenv XMODIFIERS "@im=xcin"
|
||||
|
||||
@ -1,12 +1,8 @@
|
||||
+-------------------
|
||||
|
|
||||
| minicom is installed with permissions set at 555.
|
||||
|
|
||||
| To allow users to run minicom, you should put them in group dialer.
|
||||
|
|
||||
| If you wish to use ${SYSCONFDIR}/minicom/minicom.users to restrict
|
||||
| user behaviour to specific configurations or ports, then you
|
||||
| must change the permissions on ${PREFIX}/bin/minicom to be mode 4551
|
||||
| owned by uucp:dialer and *not* put users in group dialer.
|
||||
|
|
||||
+-------------------
|
||||
minicom is installed with permissions set at 555.
|
||||
|
||||
To allow users to run minicom, you should put them in group dialer.
|
||||
|
||||
If you wish to use ${SYSCONFDIR}/minicom/minicom.users to restrict
|
||||
user behaviour to specific configurations or ports, then you
|
||||
must change the permissions on ${PREFIX}/bin/minicom to be mode 4551
|
||||
owned by uucp:dialer and *not* put users in group dialer.
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
+---------------
|
||||
| See qpage.cf in ${PREFIX}/share/examples/qpage for a sample
|
||||
| configuration file.
|
||||
|
|
||||
| Make sure you have the qpage.cf file in the /etc directory
|
||||
+---------------
|
||||
See qpage.cf in ${PREFIX}/share/examples/qpage for a sample
|
||||
configuration file.
|
||||
|
||||
Make sure you have the qpage.cf file in the /etc directory
|
||||
|
||||
@ -1,4 +1,2 @@
|
||||
+--------------------
|
||||
| If you want to activate html2wml as a CGI, then copy
|
||||
| ${PREFIX}/bin/html2wml into your cgi-bin directory.
|
||||
+--------------------
|
||||
If you want to activate html2wml as a CGI, then copy
|
||||
${PREFIX}/bin/html2wml into your cgi-bin directory.
|
||||
|
||||
@ -1,7 +1,5 @@
|
||||
------------------------------------------------------------------------
|
||||
To link against the c2hs library components, add:
|
||||
|
||||
-package c2hs
|
||||
|
||||
to the GHC command line
|
||||
------------------------------------------------------------------------
|
||||
|
||||
@ -1,6 +1,3 @@
|
||||
+---------------
|
||||
| To use the CGI, copy ${PREFIX}/libexec/darcs/darcs.cgi to the
|
||||
| cgi-bin directory. An example configuration file for the cgi is
|
||||
| in ${PREFIX}/share/darcs, and should be copied to ${SYSCONFDIR}/darcs.
|
||||
+---------------
|
||||
|
||||
To use the CGI, copy ${PREFIX}/libexec/darcs/darcs.cgi to the
|
||||
cgi-bin directory. An example configuration file for the cgi is
|
||||
in ${PREFIX}/share/darcs, and should be copied to ${SYSCONFDIR}/darcs.
|
||||
|
||||
@ -1,11 +1,7 @@
|
||||
To use the 'plot' command, install the 'math/gnuplot' port.
|
||||
|
||||
+---------------
|
||||
| To use the 'plot' command, install the 'math/gnuplot' port.
|
||||
|
|
||||
| If you select the 'plot' command without gnuplot installed you may
|
||||
| get an X error. (Clicking 'ignore' seems ok.)
|
||||
|
|
||||
| You may need to increase your memory limits when plotting
|
||||
| large arrays.
|
||||
+---------------
|
||||
If you select the 'plot' command without gnuplot installed you may
|
||||
get an X error. (Clicking 'ignore' seems ok.)
|
||||
|
||||
You may need to increase your memory limits when plotting
|
||||
large arrays.
|
||||
|
||||
@ -1,7 +1,5 @@
|
||||
------------------------------------------------------------------------
|
||||
To link against the library, add:
|
||||
|
||||
-package ports
|
||||
|
||||
to the GHC command line
|
||||
------------------------------------------------------------------------
|
||||
|
||||
@ -1,4 +1,2 @@
|
||||
+----------
|
||||
| This package requires the sysctl kern.emul.linux being set to 1 and
|
||||
| just did so. To make this change permanent, edit /etc/sysctl.conf.
|
||||
+----------
|
||||
This package requires the sysctl kern.emul.linux being set to 1 and
|
||||
just did so. To make this change permanent, edit /etc/sysctl.conf.
|
||||
|
||||
@ -1,14 +1,12 @@
|
||||
+---------------
|
||||
| To use the Java plugin with Mozilla or Mozilla-firefox you must create
|
||||
| a symbolic link from
|
||||
|
|
||||
| ${PREFIX}/${JDKHOME}/jre/plugin/i386/ns600/libjavaplugin_oji.so
|
||||
|
|
||||
| to your local Mozilla plugins directory, which is found at
|
||||
|
|
||||
| ~/.mozilla/plugins/
|
||||
|
|
||||
| or to the shared Mozilla plugins directory, which is found at
|
||||
|
|
||||
| ${PREFIX}/lib/mozilla-plugins/
|
||||
+---------------
|
||||
To use the Java plugin with Mozilla or Mozilla-firefox you must create
|
||||
a symbolic link from
|
||||
|
||||
${PREFIX}/${JDKHOME}/jre/plugin/i386/ns600/libjavaplugin_oji.so
|
||||
|
||||
to your local Mozilla plugins directory, which is found at
|
||||
|
||||
~/.mozilla/plugins/
|
||||
|
||||
or to the shared Mozilla plugins directory, which is found at
|
||||
|
||||
${PREFIX}/lib/mozilla-plugins/
|
||||
|
||||
@ -1,14 +1,12 @@
|
||||
+---------------
|
||||
| To use the Java plugin with Mozilla or Mozilla-firefox you must create
|
||||
| a symbolic link from
|
||||
|
|
||||
| ${PREFIX}/${JREHOME}/plugin/i386/ns600/libjavaplugin_oji.so
|
||||
|
|
||||
| to your local Mozilla plugins directory, which is found at
|
||||
|
|
||||
| ~/.mozilla/plugins/
|
||||
|
|
||||
| or to the shared Mozilla plugins directory, which is found at
|
||||
|
|
||||
| ${PREFIX}/lib/mozilla-plugins/
|
||||
+---------------
|
||||
To use the Java plugin with Mozilla or Mozilla-firefox you must create
|
||||
a symbolic link from
|
||||
|
||||
${PREFIX}/${JREHOME}/plugin/i386/ns600/libjavaplugin_oji.so
|
||||
|
||||
to your local Mozilla plugins directory, which is found at
|
||||
|
||||
~/.mozilla/plugins/
|
||||
|
||||
or to the shared Mozilla plugins directory, which is found at
|
||||
|
||||
${PREFIX}/lib/mozilla-plugins/
|
||||
|
||||
@ -1,19 +1,16 @@
|
||||
+----------------------
|
||||
|
|
||||
| XEmacs is pretty useless as-is. It is just an engine.
|
||||
| You need to install modules to provide your users full functionnality.
|
||||
| There is two methods to achieve this :
|
||||
| 1 - install the xemacs21-sumo package. It contains all the
|
||||
| modules currently supported by the XEmacs team.
|
||||
| It's fast, easy and your users won't ever bother you again about this.
|
||||
| On the other hand the package is quite huge.
|
||||
| 2 - you have to install by hand every XEmacs' modules as described
|
||||
| in the XEmacs documentation. (Search for "packages" in the info tree.)
|
||||
| There are a lot of interdependencies between XEmacs' modules
|
||||
| and you may end up with everything installed just as method 1 would
|
||||
| have (without the hassle).
|
||||
|
|
||||
| Note: XEmacs modules are named "packages" by the XEmacs team, the term
|
||||
| "module" is used here just to limit possible confusion with
|
||||
| OpenBSD packages.
|
||||
+----------------------
|
||||
XEmacs is pretty useless as-is. It is just an engine.
|
||||
You need to install modules to provide your users full functionnality.
|
||||
There is two methods to achieve this :
|
||||
1 - install the xemacs21-sumo package. It contains all the
|
||||
modules currently supported by the XEmacs team.
|
||||
It's fast, easy and your users won't ever bother you again about this.
|
||||
On the other hand the package is quite huge.
|
||||
2 - you have to install by hand every XEmacs' modules as described
|
||||
in the XEmacs documentation. (Search for "packages" in the info tree.)
|
||||
There are a lot of interdependencies between XEmacs' modules
|
||||
and you may end up with everything installed just as method 1 would
|
||||
have (without the hassle).
|
||||
|
||||
Note: XEmacs modules are named "packages" by the XEmacs team, the term
|
||||
"module" is used here just to limit possible confusion with
|
||||
OpenBSD packages.
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
+---------------
|
||||
| Bochs requires a .bochsrc file to be present in either your current
|
||||
| directory or your home directory before starting. A sample of the
|
||||
| .bochsrc file can be found in ${PREFIX}/share/bochs/bochsrc
|
||||
+---------------
|
||||
Bochs requires a .bochsrc file to be present in either your current
|
||||
directory or your home directory before starting. A sample of the
|
||||
.bochsrc file can be found in ${PREFIX}/share/bochs/bochsrc
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
+----------------------------------------------------------------------
|
||||
| This package installed a setuid root executable in
|
||||
| ${PREFIX}/bin/uum. This code has not been checked for errors
|
||||
| and you are advised to avoid using it as it presents a potential
|
||||
| security risk for your system.
|
||||
+----------------------------------------------------------------------
|
||||
This package installed a setuid root executable in
|
||||
${PREFIX}/bin/uum. This code has not been checked for errors
|
||||
and you are advised to avoid using it as it presents a potential
|
||||
security risk for your system.
|
||||
|
||||
@ -1,4 +1,2 @@
|
||||
+---------------
|
||||
| To use abook from mutt add the following to your muttrc:
|
||||
| set query_command="${PREFIX}/bin/abook --mutt-query '%s'"
|
||||
+---------------
|
||||
To use abook from mutt add the following to your muttrc:
|
||||
set query_command="${PREFIX}/bin/abook --mutt-query '%s'"
|
||||
|
||||
@ -1,12 +1,10 @@
|
||||
+-------------------
|
||||
| Setuid note:
|
||||
|
|
||||
| If you intend to use Evolution to read local mail-spool mbox files then
|
||||
| you will need to set the setuid bit for the camel-lock-helper program.
|
||||
|
|
||||
| You can do this by: 'chmod u+s ${PREFIX}/sbin/camel-lock-helper'
|
||||
|
|
||||
| While there are no known security problems at this time with
|
||||
| camel-lock-helper, setting the setuid bit on any program is a
|
||||
| potential security risk.
|
||||
+-------------------
|
||||
Setuid note:
|
||||
|
||||
If you intend to use Evolution to read local mail-spool mbox files then
|
||||
you will need to set the setuid bit for the camel-lock-helper program.
|
||||
|
||||
You can do this by: 'chmod u+s ${PREFIX}/sbin/camel-lock-helper'
|
||||
|
||||
While there are no known security problems at this time with
|
||||
camel-lock-helper, setting the setuid bit on any program is a
|
||||
potential security risk.
|
||||
|
||||
@ -1,9 +1,7 @@
|
||||
+---------------
|
||||
| Mailman needs quite some configuration. Have a look at
|
||||
| ${PREFIX}/share/doc/mailman/README.OpenBSD to find out
|
||||
| what you have to do, to get mailman up and running.
|
||||
|
|
||||
| If you are upgrading from mailman 2.0.x make sure to read
|
||||
| ${PREFIX}/share/doc/mailman/UPGRADING and run
|
||||
| ${PREFIX}/lib/mailman/bin/update as root.
|
||||
+---------------
|
||||
Mailman needs quite some configuration. Have a look at
|
||||
${PREFIX}/share/doc/mailman/README.OpenBSD to find out
|
||||
what you have to do, to get mailman up and running.
|
||||
|
||||
If you are upgrading from mailman 2.0.x make sure to read
|
||||
${PREFIX}/share/doc/mailman/UPGRADING and run
|
||||
${PREFIX}/lib/mailman/bin/update as root.
|
||||
|
||||
@ -1,16 +1,14 @@
|
||||
+---------------
|
||||
| milter-regex has been installed as ${PREFIX}/libexec/milter-regex.
|
||||
| See milter-regex(8) for instructions on how to register the plugin.
|
||||
|
|
||||
| To start the plugin automatically on startup, one can use:
|
||||
|
|
||||
| /etc/rc.conf.local
|
||||
| milter_regex=YES
|
||||
|
|
||||
| /etc/rc.local
|
||||
| if [ X"${milter_regex}" == X"YES" -a \
|
||||
| -x ${PREFIX}/libexec/milter-regex ]; then
|
||||
| echo -n ' milter-regex'
|
||||
| ${PREFIX}/libexec/milter-regex
|
||||
| fi
|
||||
+---------------
|
||||
milter-regex has been installed as ${PREFIX}/libexec/milter-regex.
|
||||
See milter-regex(8) for instructions on how to register the plugin.
|
||||
|
||||
To start the plugin automatically on startup, one can use:
|
||||
|
||||
/etc/rc.conf.local
|
||||
milter_regex=YES
|
||||
|
||||
/etc/rc.local
|
||||
if [ X"${milter_regex}" == X"YES" -a \
|
||||
-x ${PREFIX}/libexec/milter-regex ]; then
|
||||
echo -n ' milter-regex'
|
||||
${PREFIX}/libexec/milter-regex
|
||||
fi
|
||||
|
||||
@ -1,16 +1,14 @@
|
||||
+---------------
|
||||
| milter-spamd has been installed as ${PREFIX}/libexec/milter-spamd.
|
||||
| See milter-spamd(8) for instructions on how to register the plugin.
|
||||
|
|
||||
| To start the plugin automatically on startup, one can use:
|
||||
|
|
||||
| /etc/rc.conf.local
|
||||
| milter_spamd=""
|
||||
|
|
||||
| /etc/rc.local
|
||||
| if [ X"${milter_spamd}" != X"NO" -a \
|
||||
| -x ${PREFIX}/libexec/milter-spamd ]; then
|
||||
| echo -n ' milter-spamd'
|
||||
| ${PREFIX}/libexec/milter-spamd ${milter_spamd}
|
||||
| fi
|
||||
+---------------
|
||||
milter-spamd has been installed as ${PREFIX}/libexec/milter-spamd.
|
||||
See milter-spamd(8) for instructions on how to register the plugin.
|
||||
|
||||
To start the plugin automatically on startup, one can use:
|
||||
|
||||
/etc/rc.conf.local
|
||||
milter_spamd=""
|
||||
|
||||
/etc/rc.local
|
||||
if [ X"${milter_spamd}" != X"NO" -a \
|
||||
-x ${PREFIX}/libexec/milter-spamd ]; then
|
||||
echo -n ' milter-spamd'
|
||||
${PREFIX}/libexec/milter-spamd ${milter_spamd}
|
||||
fi
|
||||
|
||||
@ -1,14 +1,10 @@
|
||||
For using anonymous remailers, up-to-date public key rings are a necessity.
|
||||
You should fetch these at least daily and provide them to your users.
|
||||
${PREFIX}/share/examples/mixmaster/mixmaster-update.pl is a sample
|
||||
script facilitating this task.
|
||||
|
||||
+-----------
|
||||
| For using anonymous remailers, up-to-date public key rings are a necessity.
|
||||
| You should fetch these at least daily and provide them to your users.
|
||||
| ${PREFIX}/share/examples/mixmaster/mixmaster-update.pl is a sample
|
||||
| script facilitating this task.
|
||||
|
|
||||
| All users have their own mixmaster configuration files and pools in
|
||||
| ~/.Mix, but global defaults can be specified in
|
||||
| ${SYSCONFDIR}/mixmaster/client.cfg. You might want to specify PUBRING and
|
||||
| TYPE2REL in this file to point to some sitewide files fetched, e.g. by the
|
||||
| above mentioned script.
|
||||
+-----------
|
||||
|
||||
All users have their own mixmaster configuration files and pools in
|
||||
~/.Mix, but global defaults can be specified in
|
||||
${SYSCONFDIR}/mixmaster/client.cfg. You might want to specify PUBRING and
|
||||
TYPE2REL in this file to point to some sitewide files fetched, e.g. by the
|
||||
above mentioned script.
|
||||
|
||||
@ -1,4 +1,2 @@
|
||||
+---------------
|
||||
| If you intend to use the Tk interface, you have to install the Python
|
||||
| tkinter subpackage (lang/python/${MODPY_VERSION},-tkinter).
|
||||
+---------------
|
||||
If you intend to use the Tk interface, you have to install the Python
|
||||
tkinter subpackage (lang/python/${MODPY_VERSION},-tkinter).
|
||||
|
||||
@ -1,7 +1,5 @@
|
||||
+---------------
|
||||
| Some documentation for pine can be found in
|
||||
| ${PREFIX}/share/doc/pine as well as pine(1).
|
||||
|
|
||||
| Please read the documentation for instruction on how to make/update
|
||||
| the configuration files /etc/pine.conf and /etc/pine.conf.fixed
|
||||
+---------------
|
||||
Some documentation for pine can be found in
|
||||
${PREFIX}/share/doc/pine as well as pine(1).
|
||||
|
||||
Please read the documentation for instruction on how to make/update
|
||||
the configuration files /etc/pine.conf and /etc/pine.conf.fixed
|
||||
|
||||
@ -1,4 +1,2 @@
|
||||
+------------
|
||||
| The dillo plugin has been installed into
|
||||
| ${PREFIX}/lib/sylpheed-claws/plugins/
|
||||
+------------
|
||||
The dillo plugin has been installed into
|
||||
${PREFIX}/lib/sylpheed-claws/plugins/
|
||||
|
||||
@ -1,4 +1,2 @@
|
||||
+------------
|
||||
| The image viewer plugin has been installed into
|
||||
| ${PREFIX}/lib/sylpheed-claws/plugins/
|
||||
+------------
|
||||
The image viewer plugin has been installed into
|
||||
${PREFIX}/lib/sylpheed-claws/plugins/
|
||||
|
||||
@ -1,4 +1,2 @@
|
||||
+------------
|
||||
| The spamassassing plugin has been installed into
|
||||
| ${PREFIX}/lib/sylpheed-claws/plugins/
|
||||
+------------
|
||||
The spamassassing plugin has been installed into
|
||||
${PREFIX}/lib/sylpheed-claws/plugins/
|
||||
|
||||
@ -1,4 +1,2 @@
|
||||
+------------
|
||||
| The sylpheed-claws themes have been installed into
|
||||
| ${PREFIX}/share/sylpheed-claws/themes/
|
||||
+------------
|
||||
The sylpheed-claws themes have been installed into
|
||||
${PREFIX}/share/sylpheed-claws/themes/
|
||||
|
||||
@ -1,8 +1,3 @@
|
||||
+------------------
|
||||
|
|
||||
| Please see ${PREFIX}/share/doc/tmda/INSTALL for configuration
|
||||
| instruction, and ${PREFIX}/share/doc/tmda/UPGRADE if upgrading
|
||||
| from a previous release.
|
||||
|
|
||||
+------------------
|
||||
|
||||
Please see ${PREFIX}/share/doc/tmda/INSTALL for configuration
|
||||
instruction, and ${PREFIX}/share/doc/tmda/UPGRADE if upgrading
|
||||
from a previous release.
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
------------------------------------------------------------------------------
|
||||
===> Installing WMMail defaults in ${PREFIX}/GNUstep/Apps/WMMail.app/Defaults
|
||||
===> Modify to your config and copy to ~/GNUstep/Defaults/WMMail
|
||||
Installing WMMail defaults in ${PREFIX}/GNUstep/Apps/WMMail.app/Defaults
|
||||
Modify to your config and copy to ~/GNUstep/Defaults/WMMail
|
||||
|
||||
===> Installing README in ${PREFIX}/GNUstep/Apps/WMMail.app
|
||||
------------------------------------------------------------------------------
|
||||
Installing README in ${PREFIX}/GNUstep/Apps/WMMail.app
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
+------------
|
||||
| The ap-config systrace sample policy has been installed into
|
||||
| ${PREFIX}/share/examples/systrace. Please view this file
|
||||
| and change the policy to meet your needs. You can install this
|
||||
| file into /etc/systrace or your ~/.systrace directory.
|
||||
+------------
|
||||
The ap-config systrace sample policy has been installed into
|
||||
${PREFIX}/share/examples/systrace. Please view this file
|
||||
and change the policy to meet your needs. You can install this
|
||||
file into /etc/systrace or your ~/.systrace directory.
|
||||
|
||||
@ -1,12 +1,10 @@
|
||||
+------------
|
||||
| To have snmpd start at boot time, you must edit ${SYSCONFDIR}/snmp/snmpd.conf
|
||||
| and uncomment the following in /etc/rc.local.
|
||||
|
|
||||
| #if [ -x /usr/local/sbin/snmpd ]; then
|
||||
| # echo -n ' snmpd'; /usr/local/sbin/snmpd
|
||||
| #fi
|
||||
|
|
||||
| This will start snmpd and use ${SYSCONFDIR}/snmp/snmpd.conf for the configuration.
|
||||
| The snmpconf tool can be used to help edit your configuration files. See
|
||||
| snmpconf(1), snmpd(8), and snmpd.conf(5) for more options.
|
||||
+------------
|
||||
To have snmpd start at boot time, you must edit ${SYSCONFDIR}/snmp/snmpd.conf
|
||||
and uncomment the following in /etc/rc.local.
|
||||
|
||||
#if [ -x /usr/local/sbin/snmpd ]; then
|
||||
# echo -n ' snmpd'; /usr/local/sbin/snmpd
|
||||
#fi
|
||||
|
||||
This will start snmpd and use ${SYSCONFDIR}/snmp/snmpd.conf for the configuration.
|
||||
The snmpconf tool can be used to help edit your configuration files. See
|
||||
snmpconf(1), snmpd(8), and snmpd.conf(5) for more options.
|
||||
|
||||
@ -1,10 +1,8 @@
|
||||
+------------
|
||||
| TACACS+ requires root privileges to start up properly. After the
|
||||
| initialization, it will drop privileges to a less-privileged
|
||||
| user/group called '${TACACSUSER}'.
|
||||
|
|
||||
| Please edit /etc/services and add the following entry:
|
||||
|
|
||||
| tacacs+ 49/tcp
|
||||
|
|
||||
+------------
|
||||
TACACS+ requires root privileges to start up properly. After the
|
||||
initialization, it will drop privileges to a less-privileged
|
||||
user/group called '${TACACSUSER}'.
|
||||
|
||||
Please edit /etc/services and add the following entry:
|
||||
|
||||
tacacs+ 49/tcp
|
||||
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
+------
|
||||
| Example files demonstrating the usage of p5-Gateway
|
||||
| have been installed into:
|
||||
|
|
||||
| ${PREFIX}/share/examples/p5-Gateway
|
||||
+-----
|
||||
Example files demonstrating the usage of p5-Gateway
|
||||
have been installed into:
|
||||
|
||||
${PREFIX}/share/examples/p5-Gateway
|
||||
|
||||
@ -1,8 +1,2 @@
|
||||
|
||||
+------------------------------------
|
||||
|
|
||||
| Be sure to read the license agreement in
|
||||
| ${PREFIX}/Acrobat5/Font/LICFONT.txt
|
||||
|
|
||||
+------------------------------------
|
||||
|
||||
Be sure to read the license agreement in
|
||||
${PREFIX}/Acrobat5/Font/LICFONT.txt
|
||||
|
||||
@ -1,9 +1,5 @@
|
||||
Be sure to read the license agreement in
|
||||
${PREFIX}/Acrobat5/Reader/license.txt
|
||||
|
||||
+------------------------------------
|
||||
| Be sure to read the license agreement in
|
||||
| ${PREFIX}/Acrobat5/Reader/license.txt
|
||||
|
|
||||
| This package requires the sysctl kern.emul.linux being set to 1 and
|
||||
| just did so. To make this change permanent, edit /etc/sysctl.conf.
|
||||
+------------------------------------
|
||||
|
||||
This package requires the sysctl kern.emul.linux being set to 1 and
|
||||
just did so. To make this change permanent, edit /etc/sysctl.conf.
|
||||
|
||||
@ -1,9 +1,5 @@
|
||||
+---------------
|
||||
|
|
||||
| To run AUC TeX on start up of emacs or xemacs add:
|
||||
|
|
||||
| (require 'tex-site)
|
||||
|
|
||||
| to your ~/.emacs file.
|
||||
|
|
||||
+---------------
|
||||
To run AUC TeX on start up of emacs or xemacs add:
|
||||
|
||||
(require 'tex-site)
|
||||
|
||||
to your ~/.emacs file.
|
||||
|
||||
@ -1,16 +1,14 @@
|
||||
+---------------
|
||||
| To install these fonts for X11, just make sure that the fontpath
|
||||
| lists the 75dpi or 100dpi bitmap fonts before the ghostscript fonts,
|
||||
| and make sure you have the string ":unscaled" appended to the bitmap
|
||||
| font's fontpath. This way, the bitmap fonts will be used if they
|
||||
| match, and the Type 1 versions will be used if the font needs to be
|
||||
| scaled. Below is the relevant section from a typical XF86Config-4
|
||||
| file.
|
||||
|
|
||||
| FontPath "/usr/X11R6/lib/X11/fonts/misc/"
|
||||
| FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
|
||||
| FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
|
||||
| FontPath "/usr/local/lib/X11/fonts/ghostscript/"
|
||||
| FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
|
||||
|
|
||||
+---------------
|
||||
To install these fonts for X11, just make sure that the fontpath
|
||||
lists the 75dpi or 100dpi bitmap fonts before the ghostscript fonts,
|
||||
and make sure you have the string ":unscaled" appended to the bitmap
|
||||
font's fontpath. This way, the bitmap fonts will be used if they
|
||||
match, and the Type 1 versions will be used if the font needs to be
|
||||
scaled. Below is the relevant section from a typical XF86Config-4
|
||||
file.
|
||||
|
||||
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
|
||||
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
|
||||
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
|
||||
FontPath "/usr/local/lib/X11/fonts/ghostscript/"
|
||||
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
|
||||
|
||||
|
||||
@ -1,10 +1,8 @@
|
||||
+------
|
||||
| You will have to specify the datadir manually
|
||||
| every time you use htmldoc. Try:
|
||||
|
|
||||
| htmldoc --datadir ${PREFIX}/share/htmldoc
|
||||
|
|
||||
| The full set of documentation is available online:
|
||||
|
|
||||
| ${HOMEPAGE}/htmldoc.html
|
||||
+------
|
||||
You will have to specify the datadir manually
|
||||
every time you use htmldoc. Try:
|
||||
|
||||
htmldoc --datadir ${PREFIX}/share/htmldoc
|
||||
|
||||
The full set of documentation is available online:
|
||||
|
||||
${HOMEPAGE}/htmldoc.html
|
||||
|
||||
@ -1,7 +1,5 @@
|
||||
+---------------
|
||||
| The main features of this software are the creation of PDF
|
||||
| presentations and transparencies using ghostscript.
|
||||
|
|
||||
| Ghostscript is NOT necessary to run prosper but you are going
|
||||
| to need it if you want to make something useful.
|
||||
+---------------
|
||||
The main features of this software are the creation of PDF
|
||||
presentations and transparencies using ghostscript.
|
||||
|
||||
Ghostscript is NOT necessary to run prosper but you are going
|
||||
to need it if you want to make something useful.
|
||||
|
||||
@ -1,11 +1,7 @@
|
||||
CFS is started automatically in /etc/rc.local. In order for it to work
|
||||
properly, you have to do these steps as root:
|
||||
|
||||
+----------
|
||||
| CFS is started automatically in /etc/rc.local. In order for it to work
|
||||
| properly, you have to do these steps as root:
|
||||
|
|
||||
| 0) add this line to /etc/exports
|
||||
| /null localhost
|
||||
| 1) set "nfs_server=YES" in /etc/rc.conf
|
||||
| 2) reboot or start mountd and cfsd by hand and mount /crypt
|
||||
+----------
|
||||
|
||||
0) add this line to /etc/exports
|
||||
/null localhost
|
||||
1) set "nfs_server=YES" in /etc/rc.conf
|
||||
2) reboot or start mountd and cfsd by hand and mount /crypt
|
||||
|
||||
@ -1,7 +1,5 @@
|
||||
------------------------------------------------------------------------
|
||||
To link against the library, add:
|
||||
|
||||
-package crypto
|
||||
|
||||
to the GHC command line
|
||||
------------------------------------------------------------------------
|
||||
|
||||
@ -1,7 +1,3 @@
|
||||
|
||||
+---------------
|
||||
| If you have not already installed nmap 3.00 or a newer version
|
||||
| in ${PREFIX}/bin, you may wish to do so in order to enable some
|
||||
| checks which will otherwise return false negatives.
|
||||
+---------------
|
||||
|
||||
If you have not already installed nmap 3.00 or a newer version
|
||||
in ${PREFIX}/bin, you may wish to do so in order to enable some
|
||||
checks which will otherwise return false negatives.
|
||||
|
||||
@ -1,4 +1,3 @@
|
||||
----------------------------------------------------------------------
|
||||
There are a number of large changes from the 2.6.2 distribution. Most
|
||||
notable is that the command line has changed substantially. See
|
||||
the pgp5(1) man page for a discussion of how to use the new command
|
||||
@ -18,4 +17,3 @@ should copy them yourself. Note that copying language.txt to
|
||||
language50.txt is a decidedly bad idea. Also note that language50.txt
|
||||
is entirely optional; US English is the only language it contains at
|
||||
this time.
|
||||
----------------------------------------------------------------------
|
||||
|
||||
@ -1,9 +1,7 @@
|
||||
+------------
|
||||
| To have monit start at boot time, you must have an entry similar to the
|
||||
| following in /etc/rc.local.
|
||||
|
|
||||
| if [ -x ${PREFIX}/bin/monit ]; then
|
||||
| echo -n ' monit'; ${PREFIX}/bin/monit \
|
||||
| -d 300 -c ${SYSCONFDIR}/monitrc >/dev/null 2>&1
|
||||
| fi
|
||||
+------------
|
||||
To have monit start at boot time, you must have an entry similar to the
|
||||
following in /etc/rc.local.
|
||||
|
||||
if [ -x ${PREFIX}/bin/monit ]; then
|
||||
echo -n ' monit'; ${PREFIX}/bin/monit \
|
||||
-d 300 -c ${SYSCONFDIR}/monitrc >/dev/null 2>&1
|
||||
fi
|
||||
|
||||
@ -1,16 +1,14 @@
|
||||
+--------------- nut
|
||||
| Using the Nut package in an OpenBSD environment:
|
||||
|
|
||||
| Once you have the config files under /etc/nut set up properly, the
|
||||
| following block can be added to your /etc/rc.local file to start nut.
|
||||
|
|
||||
| # Start Nut
|
||||
| if [ -x ${PREFIX}/bin/upsdrvctl ]; then
|
||||
| echo -n ' nut'
|
||||
| ${PREFIX}/bin/upsdrvctl start > /dev/null 2>&1
|
||||
| ${PREFIX}/sbin/upsd > /dev/null 2>&1
|
||||
| ${PREFIX}/sbin/upsmon > /dev/null 2>&1
|
||||
| fi
|
||||
|
|
||||
| You may also be interested in the "-i" flag to upsd, see upsd(8).
|
||||
+--------------- nut
|
||||
Using the Nut package in an OpenBSD environment:
|
||||
|
||||
Once you have the config files under /etc/nut set up properly, the
|
||||
following block can be added to your /etc/rc.local file to start nut.
|
||||
|
||||
# Start Nut
|
||||
if [ -x ${PREFIX}/bin/upsdrvctl ]; then
|
||||
echo -n ' nut'
|
||||
${PREFIX}/bin/upsdrvctl start > /dev/null 2>&1
|
||||
${PREFIX}/sbin/upsd > /dev/null 2>&1
|
||||
${PREFIX}/sbin/upsmon > /dev/null 2>&1
|
||||
fi
|
||||
|
||||
You may also be interested in the "-i" flag to upsd, see upsd(8).
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
+---------------
|
||||
| Please see ${PREFIX}/rtty for setup instructions.
|
||||
| You will probably want to run ${PREFIX}/rtty/bin/Startup
|
||||
| from /etc/rc.local.
|
||||
+---------------
|
||||
Please see ${PREFIX}/rtty for setup instructions.
|
||||
You will probably want to run ${PREFIX}/rtty/bin/Startup
|
||||
from /etc/rc.local.
|
||||
|
||||
@ -1,8 +1,7 @@
|
||||
---------------------------
|
||||
| You will need to add
|
||||
| csh -cf '/usr/local/sbin/runsvdir-start &'
|
||||
| to /etc/rc.local in order to have runit start at boot.
|
||||
| The port expects services to be in /service. If you're
|
||||
| using another location you will have to modify
|
||||
| runsvdir-start.
|
||||
You will need to add
|
||||
|
||||
csh -cf '/usr/local/sbin/runsvdir-start &'
|
||||
|
||||
to /etc/rc.local in order to have runit start at boot. The port expects
|
||||
services to be in /service. If you're using another location you will
|
||||
have to modify runsvdir-start.
|
||||
|
||||
@ -1,10 +1,8 @@
|
||||
+---------------
|
||||
| Example configurations for both symon and symux have been installed
|
||||
| in ${PREFIX}/share/examples/symon.
|
||||
|
|
||||
| RRD files can be obtained by running
|
||||
| ${PREFIX}/share/symon/c_smrrds.sh
|
||||
|
|
||||
| Read the LEGACY section of symux(8) for information about
|
||||
| migrating RRDs from a previous symux version.
|
||||
+---------------
|
||||
Example configurations for both symon and symux have been installed
|
||||
in ${PREFIX}/share/examples/symon.
|
||||
|
||||
RRD files can be obtained by running
|
||||
${PREFIX}/share/symon/c_smrrds.sh
|
||||
|
||||
Read the LEGACY section of symux(8) for information about
|
||||
migrating RRDs from a previous symux version.
|
||||
|
||||
@ -1,4 +1,2 @@
|
||||
+---------------
|
||||
| An example configuration for symon has been installed in
|
||||
| ${PREFIX}/share/examples/symon.
|
||||
+---------------
|
||||
An example configuration for symon has been installed in
|
||||
${PREFIX}/share/examples/symon.
|
||||
|
||||
@ -1,10 +1,8 @@
|
||||
+---------------
|
||||
| An example configuration for symux has been installed in
|
||||
| ${PREFIX}/share/examples/symon.
|
||||
|
|
||||
| RRD files can be obtained by running
|
||||
| ${PREFIX}/share/symon/c_smrrds.sh
|
||||
|
|
||||
| Read the LEGACY section of symux(8) for information about
|
||||
| migrating RRDs from a previous symux version.
|
||||
+---------------
|
||||
An example configuration for symux has been installed in
|
||||
${PREFIX}/share/examples/symon.
|
||||
|
||||
RRD files can be obtained by running
|
||||
${PREFIX}/share/symon/c_smrrds.sh
|
||||
|
||||
Read the LEGACY section of symux(8) for information about
|
||||
migrating RRDs from a previous symux version.
|
||||
|
||||
@ -1,17 +1,15 @@
|
||||
+---------------------------------------------------
|
||||
| The X11 fonts for ${PKGNAME} have been installed to
|
||||
|
|
||||
| ${FONTDIR}
|
||||
|
|
||||
| You must add them to your X11 font paths with the
|
||||
| following command:
|
||||
|
|
||||
| xset +fp ${FONTDIR}
|
||||
|
|
||||
| To enable this permanently when the X11 server is
|
||||
| started, add
|
||||
|
|
||||
| FontPath "${FONTDIR}"
|
||||
|
|
||||
| in the "Files" section of your XF86Config file.
|
||||
+---------------------------------------------------
|
||||
The X11 fonts for ${PKGNAME} have been installed to
|
||||
|
||||
${FONTDIR}
|
||||
|
||||
You must add them to your X11 font paths with the
|
||||
following command:
|
||||
|
||||
xset +fp ${FONTDIR}
|
||||
|
||||
To enable this permanently when the X11 server is
|
||||
started, add
|
||||
|
||||
FontPath "${FONTDIR}"
|
||||
|
||||
in the "Files" section of your XF86Config file.
|
||||
|
||||
@ -1,9 +1,5 @@
|
||||
+---------------
|
||||
|
|
||||
| If X support was enabled, run:
|
||||
|
|
||||
| ${PREFIX}/bin/links -g ${PREFIX}/share/links+/calibration.html
|
||||
|
|
||||
| and proceed with the calibration of your monitor and Links.
|
||||
|
|
||||
+---------------
|
||||
If X support was enabled, run:
|
||||
|
||||
${PREFIX}/bin/links -g ${PREFIX}/share/links+/calibration.html
|
||||
|
||||
and proceed with the calibration of your monitor and Links.
|
||||
|
||||
@ -1,10 +1,8 @@
|
||||
+---------------
|
||||
| To finish the install of mod_auth_bsd, you need
|
||||
| to enable the module using the following command:
|
||||
|
|
||||
| # ${PREFIX}/sbin/mod_auth_bsd-enable
|
||||
|
|
||||
| If you already have Apache running on your machine,
|
||||
| you should not use "apachectl restart" - instead,
|
||||
| you should fully stop and then restart the server.
|
||||
+---------------
|
||||
To finish the install of mod_auth_bsd, you need
|
||||
to enable the module using the following command:
|
||||
|
||||
# ${PREFIX}/sbin/mod_auth_bsd-enable
|
||||
|
||||
If you already have Apache running on your machine,
|
||||
you should not use "apachectl restart" - instead,
|
||||
you should fully stop and then restart the server.
|
||||
|
||||
@ -1,10 +1,8 @@
|
||||
+---------------
|
||||
| To finish the install of mod_auth_ldap, you need
|
||||
| to enable the module using the following command
|
||||
|
|
||||
| ${PREFIX}/sbin/mod_auth_ldap-enable
|
||||
|
|
||||
| If you already have Apache running on your machine,
|
||||
| you should not use "apachectl restart" - instead,
|
||||
| you should fully stop and then restart the server.
|
||||
+---------------
|
||||
To finish the install of mod_auth_ldap, you need
|
||||
to enable the module using the following command
|
||||
|
||||
${PREFIX}/sbin/mod_auth_ldap-enable
|
||||
|
||||
If you already have Apache running on your machine,
|
||||
you should not use "apachectl restart" - instead,
|
||||
you should fully stop and then restart the server.
|
||||
|
||||
@ -1,13 +1,11 @@
|
||||
+---------------
|
||||
| To finish the install of mod_auth_mysql, you need
|
||||
| to enable the module using the following command
|
||||
|
|
||||
| ${PREFIX}/sbin/mod_auth_mysql-enable
|
||||
|
|
||||
| You should also read
|
||||
| ${PREFIX}/share/doc/mod_auth_mysql/USAGE
|
||||
|
|
||||
| If you already have Apache running on your machine,
|
||||
| you should not use "apachectl restart" - instead,
|
||||
| you should fully stop and then restart the server.
|
||||
+---------------
|
||||
To finish the install of mod_auth_mysql, you need
|
||||
to enable the module using the following command
|
||||
|
||||
${PREFIX}/sbin/mod_auth_mysql-enable
|
||||
|
||||
You should also read
|
||||
${PREFIX}/share/doc/mod_auth_mysql/USAGE
|
||||
|
||||
If you already have Apache running on your machine,
|
||||
you should not use "apachectl restart" - instead,
|
||||
you should fully stop and then restart the server.
|
||||
|
||||
@ -1,13 +1,11 @@
|
||||
+---------------
|
||||
| To finish the install of mod_auth_radius, you need
|
||||
| to enable the module using the following command
|
||||
|
|
||||
| ${PREFIX}/sbin/mod_auth_radius-enable
|
||||
|
|
||||
| Also, copy the following file into your Apache config:
|
||||
| ${PREFIX}/share/examples/mod_auth_radius/httpd.conf-example
|
||||
|
|
||||
| If you already have Apache running on your machine,
|
||||
| you should not use "apachectl restart" - instead,
|
||||
| you should fully stop and then restart the server.
|
||||
+---------------
|
||||
To finish the install of mod_auth_radius, you need
|
||||
to enable the module using the following command
|
||||
|
||||
${PREFIX}/sbin/mod_auth_radius-enable
|
||||
|
||||
Also, copy the following file into your Apache config:
|
||||
${PREFIX}/share/examples/mod_auth_radius/httpd.conf-example
|
||||
|
||||
If you already have Apache running on your machine,
|
||||
you should not use "apachectl restart" - instead,
|
||||
you should fully stop and then restart the server.
|
||||
|
||||
@ -1,10 +1,8 @@
|
||||
+---------------
|
||||
| To finish the install of ${PKGNAME}, you need
|
||||
| to enable the module using the following command
|
||||
|
|
||||
| ${PREFIX}/sbin/mod_dav-enable
|
||||
|
|
||||
| If you already have Apache running on your machine,
|
||||
| you should not use "apachectl restart" - instead,
|
||||
| you should fully stop and then restart the server.
|
||||
+---------------
|
||||
To finish the install of ${PKGNAME}, you need
|
||||
to enable the module using the following command
|
||||
|
||||
${PREFIX}/sbin/mod_dav-enable
|
||||
|
||||
If you already have Apache running on your machine,
|
||||
you should not use "apachectl restart" - instead,
|
||||
you should fully stop and then restart the server.
|
||||
|
||||
@ -1,10 +1,8 @@
|
||||
+---------------
|
||||
| To finish the install of mod_geoip, you need
|
||||
| to enable the module using the following command
|
||||
|
|
||||
| ${PREFIX}/sbin/mod_geoip-enable
|
||||
|
|
||||
| If you already have Apache running on your machine,
|
||||
| you should not use "apachectl restart" - instead,
|
||||
| you should fully stop and then restart the server.
|
||||
+---------------
|
||||
To finish the install of mod_geoip, you need
|
||||
to enable the module using the following command
|
||||
|
||||
${PREFIX}/sbin/mod_geoip-enable
|
||||
|
||||
If you already have Apache running on your machine,
|
||||
you should not use "apachectl restart" - instead,
|
||||
you should fully stop and then restart the server.
|
||||
|
||||
@ -1,15 +1,13 @@
|
||||
+---------------
|
||||
| To finish the install of ${PKGNAME}, you need
|
||||
| to enable the module using the following command
|
||||
|
|
||||
| ${PREFIX}/sbin/mod_gzip-enable
|
||||
|
|
||||
| Also, copy the following file into your Apache config:
|
||||
| ${PREFIX}/share/examples/mod_gzip/mod_gzip.conf.sample
|
||||
|
|
||||
| The manual is found at ${PREFIX}/share/doc/mod_gzip
|
||||
|
|
||||
| If you already have Apache running on your machine,
|
||||
| you should not use "apachectl restart" - instead,
|
||||
| you should fully stop and then start the server.
|
||||
+---------------
|
||||
To finish the install of ${PKGNAME}, you need
|
||||
to enable the module using the following command
|
||||
|
||||
${PREFIX}/sbin/mod_gzip-enable
|
||||
|
||||
Also, copy the following file into your Apache config:
|
||||
${PREFIX}/share/examples/mod_gzip/mod_gzip.conf.sample
|
||||
|
||||
The manual is found at ${PREFIX}/share/doc/mod_gzip
|
||||
|
||||
If you already have Apache running on your machine,
|
||||
you should not use "apachectl restart" - instead,
|
||||
you should fully stop and then start the server.
|
||||
|
||||
@ -1,10 +1,8 @@
|
||||
+---------------
|
||||
| To finish the install of mod_log_sql, you need
|
||||
| to enable the module using the following command
|
||||
|
|
||||
| ${PREFIX}/sbin/mod_log_sql-enable
|
||||
|
|
||||
| If you already have Apache running on your machine,
|
||||
| you should not use "apachectl restart" - instead,
|
||||
| you should fully stop and then restart the server.
|
||||
+---------------
|
||||
To finish the install of mod_log_sql, you need
|
||||
to enable the module using the following command
|
||||
|
||||
${PREFIX}/sbin/mod_log_sql-enable
|
||||
|
||||
If you already have Apache running on your machine,
|
||||
you should not use "apachectl restart" - instead,
|
||||
you should fully stop and then restart the server.
|
||||
|
||||
@ -1,21 +1,19 @@
|
||||
+---------------
|
||||
| To finish the install of mod_mp3, you need
|
||||
| to enable the module by using the following command
|
||||
|
|
||||
| ${PREFIX}/sbin/mod_mp3-enable
|
||||
|
|
||||
| Also, copy the following file into your Apache config
|
||||
| directory:
|
||||
|
|
||||
| ${PREFIX}/share/examples/mod_mp3/mp3.conf
|
||||
|
|
||||
| Add the following line to your httpd.conf:
|
||||
|
|
||||
| include conf/mp3.conf
|
||||
|
|
||||
| Edit mp3.conf to suit your needs.
|
||||
|
|
||||
| If you already have Apache running on your machine,
|
||||
| you should not use "apachectl restart" - instead,
|
||||
| you should fully stop and then restart the server.
|
||||
+---------------
|
||||
To finish the install of mod_mp3, you need
|
||||
to enable the module by using the following command
|
||||
|
||||
${PREFIX}/sbin/mod_mp3-enable
|
||||
|
||||
Also, copy the following file into your Apache config
|
||||
directory:
|
||||
|
||||
${PREFIX}/share/examples/mod_mp3/mp3.conf
|
||||
|
||||
Add the following line to your httpd.conf:
|
||||
|
||||
include conf/mp3.conf
|
||||
|
||||
Edit mp3.conf to suit your needs.
|
||||
|
||||
If you already have Apache running on your machine,
|
||||
you should not use "apachectl restart" - instead,
|
||||
you should fully stop and then restart the server.
|
||||
|
||||
@ -1,10 +1,8 @@
|
||||
+---------------
|
||||
| To finish the install of ${PKGNAME}, you need
|
||||
| to enable the module using the following command
|
||||
|
|
||||
| ${PREFIX}/sbin/mod_perl-enable
|
||||
|
|
||||
| If you already have Apache running on your machine,
|
||||
| you should not use "apachectl restart" - instead,
|
||||
| you should fully stop and then restart the server.
|
||||
+---------------
|
||||
To finish the install of ${PKGNAME}, you need
|
||||
to enable the module using the following command
|
||||
|
||||
${PREFIX}/sbin/mod_perl-enable
|
||||
|
||||
If you already have Apache running on your machine,
|
||||
you should not use "apachectl restart" - instead,
|
||||
you should fully stop and then restart the server.
|
||||
|
||||
@ -1,12 +1,10 @@
|
||||
+---------------
|
||||
| To finish the install of ${PKGNAME}, you need
|
||||
| to enable the module using the following command
|
||||
|
|
||||
| ${PREFIX}/sbin/mod_security-enable
|
||||
|
|
||||
| The manual is found at ${PREFIX}/share/doc/mod_security
|
||||
|
|
||||
| If you already have Apache running on your machine,
|
||||
| you should not use "apachectl restart" - instead,
|
||||
| you should fully stop and then start the server.
|
||||
+---------------
|
||||
To finish the install of ${PKGNAME}, you need
|
||||
to enable the module using the following command
|
||||
|
||||
${PREFIX}/sbin/mod_security-enable
|
||||
|
||||
The manual is found at ${PREFIX}/share/doc/mod_security
|
||||
|
||||
If you already have Apache running on your machine,
|
||||
you should not use "apachectl restart" - instead,
|
||||
you should fully stop and then start the server.
|
||||
|
||||
@ -1,9 +1,8 @@
|
||||
Netscape Communicator 4.8
|
||||
---------------------------------------------------
|
||||
|
||||
This version of Netscape has known security issues.
|
||||
You are using this *AT YOUR OWN RISK*.
|
||||
---------------------------------------------------
|
||||
|
||||
This package requires the sysctl kern.emul.${EMUL_TYPE}
|
||||
being set to 1 and just did so. To make this change
|
||||
permanent, edit /etc/sysctl.conf.
|
||||
---------------------------------------------------
|
||||
|
||||
@ -1,9 +1,8 @@
|
||||
Netscape Communicator 4.61, Fortified
|
||||
---------------------------------------------------
|
||||
|
||||
This version of Netscape has known security issues.
|
||||
You are using this *AT YOUR OWN RISK*.
|
||||
---------------------------------------------------
|
||||
|
||||
This package requires the sysctl kern.emul.${EMUL_TYPE}
|
||||
being set to 1 and just did so. To make this change
|
||||
permanent, edit /etc/sysctl.conf.
|
||||
---------------------------------------------------
|
||||
|
||||
@ -1,9 +1,8 @@
|
||||
Netscape Navigator 4.8
|
||||
---------------------------------------------------
|
||||
|
||||
This version of Netscape has known security issues.
|
||||
You are using this *AT YOUR OWN RISK*.
|
||||
---------------------------------------------------
|
||||
|
||||
This package requires the sysctl kern.emul.${EMUL_TYPE}
|
||||
being set to 1 and just did so. To make this change
|
||||
permanent, edit /etc/sysctl.conf.
|
||||
---------------------------------------------------
|
||||
|
||||
@ -1,9 +1,8 @@
|
||||
Netscape Navigator 4.61, Fortified
|
||||
---------------------------------------------------
|
||||
|
||||
This version of Netscape has known security issues.
|
||||
You are using this *AT YOUR OWN RISK*.
|
||||
---------------------------------------------------
|
||||
|
||||
This package requires the sysctl kern.emul.${EMUL_TYPE}
|
||||
being set to 1 and just did so. To make this change
|
||||
permanent, edit /etc/sysctl.conf.
|
||||
---------------------------------------------------
|
||||
|
||||
@ -1,9 +1,8 @@
|
||||
Netscape Navigator 4.75
|
||||
---------------------------------------------------
|
||||
|
||||
This version of Netscape has known security issues.
|
||||
You are using this *AT YOUR OWN RISK*.
|
||||
---------------------------------------------------
|
||||
|
||||
This package requires the sysctl kern.emul.${EMUL_TYPE}
|
||||
being set to 1 and just did so. To make this change
|
||||
permanent, edit /etc/sysctl.conf.
|
||||
---------------------------------------------------
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
+---------------
|
||||
| Enable this module in php.ini using the following command:
|
||||
|
|
||||
| ${LOCALBASE}/sbin/phpxs -a ${MODULE_NAME}
|
||||
+---------------
|
||||
Enable this module in php.ini using the following command:
|
||||
|
||||
${LOCALBASE}/sbin/phpxs -a ${MODULE_NAME}
|
||||
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
+---------------
|
||||
| Enable this module in php.ini using the following command:
|
||||
|
|
||||
| ${LOCALBASE}/sbin/phpxs -a ${MODULE_NAME}
|
||||
+---------------
|
||||
Enable this module in php.ini using the following command:
|
||||
|
||||
${LOCALBASE}/sbin/phpxs -a ${MODULE_NAME}
|
||||
|
||||
|
||||
@ -1,9 +1,7 @@
|
||||
+---------------
|
||||
| If you already have Zope running on your machine,
|
||||
| you should restart it, this can be done from the
|
||||
| Zope Control Panel in the Zope management interface.
|
||||
|
|
||||
| If you are upgrading from a plone 1.x version, please read:
|
||||
|
|
||||
| http://plone.org/documentation/migration/2.0/guide
|
||||
+---------------
|
||||
If you already have Zope running on your machine,
|
||||
you should restart it, this can be done from the
|
||||
Zope Control Panel in the Zope management interface.
|
||||
|
||||
If you are upgrading from a plone 1.x version, please read:
|
||||
|
||||
http://plone.org/documentation/migration/2.0/guide
|
||||
|
||||
@ -1,23 +1,18 @@
|
||||
+---------------
|
||||
|
|
||||
| You may want to put the following into your /etc/rc.local:
|
||||
|
|
||||
| # start wwwoffle
|
||||
| if [ -x ${PREFIX}/sbin/wwwoffled ]; then
|
||||
| echo -n ' wwwoffled'
|
||||
| ${PREFIX}/sbin/wwwoffled -c /var/spool/wwwoffle/wwwoffle.conf \
|
||||
| -p > /var/run/wwwoffled.pid
|
||||
| fi
|
||||
|
|
||||
| in /etc/ppp/ppp.linkup:
|
||||
|
|
||||
| !bg ${PREFIX}/bin/wwwoffle -online
|
||||
|
|
||||
| in /etc/ppp/ppp.linkdown:
|
||||
|
|
||||
| !bg ${PREFIX}/bin/wwwoffle -offline
|
||||
|
|
||||
|
|
||||
| Read ${PREFIX}/share/doc/wwwoffle/* for further information.
|
||||
|
|
||||
+---------------
|
||||
You may want to put the following into your /etc/rc.local:
|
||||
|
||||
# start wwwoffle
|
||||
if [ -x ${PREFIX}/sbin/wwwoffled ]; then
|
||||
echo -n ' wwwoffled'
|
||||
${PREFIX}/sbin/wwwoffled -c /var/spool/wwwoffle/wwwoffle.conf \
|
||||
-p > /var/run/wwwoffled.pid
|
||||
fi
|
||||
|
||||
in /etc/ppp/ppp.linkup:
|
||||
|
||||
!bg ${PREFIX}/bin/wwwoffle -online
|
||||
|
||||
in /etc/ppp/ppp.linkdown:
|
||||
|
||||
!bg ${PREFIX}/bin/wwwoffle -offline
|
||||
|
||||
Read ${PREFIX}/share/doc/wwwoffle/* for further information.
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
+---------------
|
||||
| If you already have Zope running on your machine,
|
||||
| you should restart it, this can be done from the
|
||||
| Zope Control Panel in the Zope management interface.
|
||||
+---------------
|
||||
If you already have Zope running on your machine,
|
||||
you should restart it, this can be done from the
|
||||
Zope Control Panel in the Zope management interface.
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
+---------------
|
||||
| If you already have Zope running on your machine,
|
||||
| you should restart it, this can be done from the
|
||||
| Zope Control Panel in the Zope management interface.
|
||||
+---------------
|
||||
If you already have Zope running on your machine,
|
||||
you should restart it, this can be done from the
|
||||
Zope Control Panel in the Zope management interface.
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
+---------------
|
||||
| If you already have Zope running on your machine,
|
||||
| you should restart it, this can be done from the
|
||||
| Zope Control Panel in the Zope management interface.
|
||||
+---------------
|
||||
If you already have Zope running on your machine,
|
||||
you should restart it, this can be done from the
|
||||
Zope Control Panel in the Zope management interface.
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
+---------------
|
||||
| If you already have Zope running on your machine,
|
||||
| you should restart it, this can be done from the
|
||||
| Zope Control Panel in the Zope management interface.
|
||||
+---------------
|
||||
If you already have Zope running on your machine,
|
||||
you should restart it, this can be done from the
|
||||
Zope Control Panel in the Zope management interface.
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
+---------------
|
||||
| If you already have Zope running on your machine,
|
||||
| you should restart it, this can be done from the
|
||||
| Zope Control Panel in the Zope management interface.
|
||||
+---------------
|
||||
If you already have Zope running on your machine,
|
||||
you should restart it, this can be done from the
|
||||
Zope Control Panel in the Zope management interface.
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
+---------------
|
||||
| If you already have Zope running on your machine,
|
||||
| you should restart it, this can be done from the
|
||||
| Zope Control Panel in the Zope management interface.
|
||||
+---------------
|
||||
If you already have Zope running on your machine,
|
||||
you should restart it, this can be done from the
|
||||
Zope Control Panel in the Zope management interface.
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
+---------------
|
||||
| If you already have Zope running on your machine,
|
||||
| you should restart it, this can be done from the
|
||||
| Zope Control Panel in the Zope management interface.
|
||||
+---------------
|
||||
If you already have Zope running on your machine,
|
||||
you should restart it, this can be done from the
|
||||
Zope Control Panel in the Zope management interface.
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
+---------------
|
||||
| If you already have Zope running on your machine,
|
||||
| you should restart it, this can be done from the
|
||||
| Zope Control Panel in the Zope management interface.
|
||||
+---------------
|
||||
If you already have Zope running on your machine,
|
||||
you should restart it, this can be done from the
|
||||
Zope Control Panel in the Zope management interface.
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
+---------------
|
||||
| If you already have Zope running on your machine,
|
||||
| you should restart it, this can be done from the
|
||||
| Zope Control Panel in the Zope management interface.
|
||||
+---------------
|
||||
If you already have Zope running on your machine,
|
||||
you should restart it, this can be done from the
|
||||
Zope Control Panel in the Zope management interface.
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
+---------------
|
||||
| If you already have Zope running on your machine,
|
||||
| you should restart it, this can be done from the
|
||||
| Zope Control Panel in the Zope management interface.
|
||||
+---------------
|
||||
If you already have Zope running on your machine,
|
||||
you should restart it, this can be done from the
|
||||
Zope Control Panel in the Zope management interface.
|
||||
|
||||
@ -1,9 +1,7 @@
|
||||
+---------------
|
||||
| This package uses the INSTANCE_HOME installation method, as described
|
||||
| at http://www.zope.org/Members/4am/instancehome. This allows you
|
||||
| to install the Zope package once and create as many sites as you
|
||||
| want without changing your core Zope installation.
|
||||
|
|
||||
| Have a look at ${ZOPEHOME}/doc/README.OpenBSD
|
||||
| to see how to create your instance and have it start at boot time.
|
||||
+---------------
|
||||
This package uses the INSTANCE_HOME installation method, as described
|
||||
at http://www.zope.org/Members/4am/instancehome. This allows you
|
||||
to install the Zope package once and create as many sites as you
|
||||
want without changing your core Zope installation.
|
||||
|
||||
Have a look at ${ZOPEHOME}/doc/README.OpenBSD
|
||||
to see how to create your instance and have it start at boot time.
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
+---------------
|
||||
| A sample configuration file has been installed as
|
||||
|
|
||||
| ${PREFIX}/share/examples/belt/menu.conf.EXAMPLE
|
||||
|
|
||||
| You can copy it to ~/.beltconf/menu.conf and change it to suit your
|
||||
| needs.
|
||||
+---------------
|
||||
A sample configuration file has been installed as
|
||||
|
||||
${PREFIX}/share/examples/belt/menu.conf.EXAMPLE
|
||||
|
||||
You can copy it to ~/.beltconf/menu.conf and change it to suit your
|
||||
needs.
|
||||
|
||||
@ -1,9 +1,7 @@
|
||||
+---------------
|
||||
| A sample configuration file has been installed as
|
||||
|
|
||||
| ${PREFIX}/share/examples/chbg/chbgrc.sample
|
||||
|
|
||||
| You can copy it to /etc/chbgrc for systemwide or
|
||||
| to ~/.chbgrc for private use and change it to suit
|
||||
| your needs.
|
||||
+---------------
|
||||
A sample configuration file has been installed as
|
||||
|
||||
${PREFIX}/share/examples/chbg/chbgrc.sample
|
||||
|
||||
You can copy it to /etc/chbgrc for systemwide or
|
||||
to ~/.chbgrc for private use and change it to suit
|
||||
your needs.
|
||||
|
||||
@ -1,12 +1,10 @@
|
||||
+------------
|
||||
| In order to use fvwm2 as your window manager, you must change your
|
||||
| .xinitrc or .xsession appropriately and add a line similar to the
|
||||
| following:
|
||||
|
|
||||
| exec ${PREFIX}/bin/fvwm2
|
||||
|
|
||||
| Icons have been installed into ${PREFIX}/share/pixmaps/fvwm, and a system
|
||||
| wide configuration has been put in ${PREFIX}/share/fvwm/system.fvwm2rc.
|
||||
| To use your own configuration, copy ${PREFIX}/share/fvwm/system.fvwm2rc
|
||||
| to ~/.fvwm2rc and edit it as appropriate.
|
||||
+------------
|
||||
In order to use fvwm2 as your window manager, you must change your
|
||||
.xinitrc or .xsession appropriately and add a line similar to the
|
||||
following:
|
||||
|
||||
exec ${PREFIX}/bin/fvwm2
|
||||
|
||||
Icons have been installed into ${PREFIX}/share/pixmaps/fvwm, and a system
|
||||
wide configuration has been put in ${PREFIX}/share/fvwm/system.fvwm2rc.
|
||||
To use your own configuration, copy ${PREFIX}/share/fvwm/system.fvwm2rc
|
||||
to ~/.fvwm2rc and edit it as appropriate.
|
||||
|
||||
@ -1,5 +1,3 @@
|
||||
+------------
|
||||
| The icon set coming with fvwm2 has been installed into
|
||||
| ${PREFIX}/share/pixmaps/fvwm. Make sure to set your
|
||||
| ImagePath appropriately.
|
||||
+------------
|
||||
The icon set coming with fvwm2 has been installed into
|
||||
${PREFIX}/share/pixmaps/fvwm. Make sure to set your
|
||||
ImagePath appropriately.
|
||||
|
||||
@ -1,12 +1,10 @@
|
||||
+------------
|
||||
| In order to use fvwm2 as your window manager, you must change your
|
||||
| .xinitrc or .xsession appropriately and add a line similar to the
|
||||
| following:
|
||||
|
|
||||
| exec ${PREFIX}/bin/fvwm2
|
||||
|
|
||||
| System wide configuration has been put in
|
||||
| ${PREFIX}/share/fvwm/system.fvwm2rc. To use your own
|
||||
| configuration, copy ${PREFIX}/share/fvwm/system.fvwm2rc to
|
||||
| ~/.fvwm2rc and edit it as appropriate.
|
||||
+------------
|
||||
In order to use fvwm2 as your window manager, you must change your
|
||||
.xinitrc or .xsession appropriately and add a line similar to the
|
||||
following:
|
||||
|
||||
exec ${PREFIX}/bin/fvwm2
|
||||
|
||||
System wide configuration has been put in
|
||||
${PREFIX}/share/fvwm/system.fvwm2rc. To use your own
|
||||
configuration, copy ${PREFIX}/share/fvwm/system.fvwm2rc to
|
||||
~/.fvwm2rc and edit it as appropriate.
|
||||
|
||||
@ -1,12 +1,10 @@
|
||||
+------------
|
||||
| In order to use fvwm95 as your window manager, you must change your
|
||||
| .xinitrc or .xsession appropriately and add a line similar to the
|
||||
| following:
|
||||
|
|
||||
| exec ${PREFIX}/bin/fvwm95
|
||||
|
|
||||
| Icons have been installed into ${PREFIX}/icons, and a system wide
|
||||
| configuration has been put in ${PREFIX}/lib/X11/fvwm95/system.fvwm95rc. To
|
||||
| use your own configuration, copy ${PREFIX}/lib/X11/fvwm95/system.fvwm95rc to
|
||||
| ~/.fvwm95rc and edit as appropriate.
|
||||
+------------
|
||||
In order to use fvwm95 as your window manager, you must change your
|
||||
.xinitrc or .xsession appropriately and add a line similar to the
|
||||
following:
|
||||
|
||||
exec ${PREFIX}/bin/fvwm95
|
||||
|
||||
Icons have been installed into ${PREFIX}/icons, and a system wide
|
||||
configuration has been put in ${PREFIX}/lib/X11/fvwm95/system.fvwm95rc. To
|
||||
use your own configuration, copy ${PREFIX}/lib/X11/fvwm95/system.fvwm95rc to
|
||||
~/.fvwm95rc and edit as appropriate.
|
||||
|
||||
@ -1,11 +1,9 @@
|
||||
+------------
|
||||
| In order to use qvwm as your window manager, you must change your
|
||||
| .xinitrc or .xsession appropriately and add a line similar to the
|
||||
| following:
|
||||
|
|
||||
| exec ${PREFIX}/bin/qvwm
|
||||
|
|
||||
| The default configuration and icons are stored in ${PREFIX}/share/qvwm.
|
||||
| To use your own configuration, copy ${PREFIX}/share/qvwm/system.qvwmrc to
|
||||
| ~/.qvwmrc and edit as appropriate.
|
||||
+------------
|
||||
In order to use qvwm as your window manager, you must change your
|
||||
.xinitrc or .xsession appropriately and add a line similar to the
|
||||
following:
|
||||
|
||||
exec ${PREFIX}/bin/qvwm
|
||||
|
||||
The default configuration and icons are stored in ${PREFIX}/share/qvwm.
|
||||
To use your own configuration, copy ${PREFIX}/share/qvwm/system.qvwmrc to
|
||||
~/.qvwmrc and edit as appropriate.
|
||||
|
||||
@ -1,6 +1,4 @@
|
||||
+---------------
|
||||
| The multibyte character encoding support is disable by default.
|
||||
| To enable this features, please edit the file:
|
||||
|
|
||||
| ${PREFIX}/lib/X11/app-defaults/Rxvt
|
||||
+---------------
|
||||
The multibyte character encoding support is disable by default.
|
||||
To enable this features, please edit the file:
|
||||
|
||||
${PREFIX}/lib/X11/app-defaults/Rxvt
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
+---------------
|
||||
| wxWidgets normally installs a symlink from wx-config to the config
|
||||
| script which is specific to the GUI library.
|
||||
|
|
||||
| OpenBSD supports installing multiple GUI libraries side-by-side, so you
|
||||
| must either call the script directly (eg wxgtk-2.4-config), or set an
|
||||
| environment variable WXCONFIG before calling wx-config.
|
||||
+---------------
|
||||
wxWidgets normally installs a symlink from wx-config to the config
|
||||
script which is specific to the GUI library.
|
||||
|
||||
OpenBSD supports installing multiple GUI libraries side-by-side, so you
|
||||
must either call the script directly (eg wxgtk-2.4-config), or set an
|
||||
environment variable WXCONFIG before calling wx-config.
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
+---------------
|
||||
| wxWidgets normally installs a symlink from wx-config to the config
|
||||
| script which is specific to the GUI library.
|
||||
|
|
||||
| OpenBSD supports installing multiple GUI libraries side-by-side, so you
|
||||
| must either call the script directly (eg wxgtk-2.4-config), or set an
|
||||
| environment variable WXCONFIG before calling wx-config.
|
||||
+---------------
|
||||
wxWidgets normally installs a symlink from wx-config to the config
|
||||
script which is specific to the GUI library.
|
||||
|
||||
OpenBSD supports installing multiple GUI libraries side-by-side, so you
|
||||
must either call the script directly (eg wxgtk-2.4-config), or set an
|
||||
environment variable WXCONFIG before calling wx-config.
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
+---------------
|
||||
| wxWidgets normally installs a symlink from wx-config to the config
|
||||
| script which is specific to the GUI library.
|
||||
|
|
||||
| OpenBSD supports installing multiple GUI libraries side-by-side, so you
|
||||
| must either call the script directly (eg wxgtk-2.4-config), or set an
|
||||
| environment variable WXCONFIG before calling wx-config.
|
||||
+---------------
|
||||
wxWidgets normally installs a symlink from wx-config to the config
|
||||
script which is specific to the GUI library.
|
||||
|
||||
OpenBSD supports installing multiple GUI libraries side-by-side, so you
|
||||
must either call the script directly (eg wxgtk-2.4-config), or set an
|
||||
environment variable WXCONFIG before calling wx-config.
|
||||
|
||||
@ -1,8 +1,6 @@
|
||||
+---------------
|
||||
| wxWidgets normally installs a symlink from wx-config to the config
|
||||
| script which is specific to the GUI library.
|
||||
|
|
||||
| OpenBSD supports installing multiple GUI libraries side-by-side, so you
|
||||
| must either call the script directly (eg wxgtk-2.4-config), or set an
|
||||
| environment variable WXCONFIG before calling wx-config.
|
||||
+---------------
|
||||
wxWidgets normally installs a symlink from wx-config to the config
|
||||
script which is specific to the GUI library.
|
||||
|
||||
OpenBSD supports installing multiple GUI libraries side-by-side, so you
|
||||
must either call the script directly (eg wxgtk-2.4-config), or set an
|
||||
environment variable WXCONFIG before calling wx-config.
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user