Add a consistent header that substitutes FULLPKGNAME for the READMEs.

ok jasper@ sthen@
This commit is contained in:
ajacoutot 2011-06-02 13:41:36 +00:00
parent 1ae40ad955
commit f982995f2b
238 changed files with 909 additions and 587 deletions

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.18 2010/12/02 22:17:46 dcoppa Exp $
# $OpenBSD: Makefile,v 1.19 2011/06/02 13:41:36 ajacoutot Exp $
SHARED_ONLY = Yes
@ -7,7 +7,7 @@ COMMENT = low latency sound server
V = 0.116.1
DISTNAME = jack-audio-connection-kit-${V}
PKGNAME = jack-${V}
REVISION = 7
REVISION = 8
SHARED_LIBS += jack 0.0 # 0.28
SHARED_LIBS += jackserver 0.0 # 0.28

View File

@ -1,7 +1,8 @@
$OpenBSD: README,v 1.2 2010/11/23 18:14:02 jasper Exp $
$OpenBSD: README,v 1.3 2011/06/02 13:41:36 ajacoutot Exp $
Running Jackd on OpenBSD
========================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
In this package of jackd, the 'dummy' and 'sndio' drivers are supported.
The 'dummy' driver is mostly useful for testing jackd itself. The

View File

@ -1,9 +1,11 @@
# $OpenBSD: Makefile,v 1.62 2011/05/24 16:24:35 giovanni Exp $
# $OpenBSD: Makefile,v 1.63 2011/06/02 13:41:36 ajacoutot Exp $
COMMENT= send/receive faxes and share modems
DISTNAME= hylafax-6.0.5
CATEGORIES= comms
REVISION= 0
HOMEPAGE= http://www.HylaFAX.org/
MAINTAINER= Giovanni Bechis <giovanni@openbsd.org>

View File

@ -1,10 +1,11 @@
$OpenBSD: README,v 1.5 2011/05/24 16:24:35 giovanni Exp $
$OpenBSD: README,v 1.6 2011/06/02 13:41:36 ajacoutot Exp $
Running Hylafax on OpenBSD
==========================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Post-installation steps:
------------------------
Post-installation steps
=======================
Hylafax needs some manual configuration before it is usable.
Make sure that you have configured HylaFAX before running faxq:
@ -22,6 +23,6 @@ something like this:
and send a SIGHUP to init(8).
References:
-----------
References
==========
Additional documentation at http://www.hylafax.org/.

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.13 2011/05/22 14:03:39 jasper Exp $
# $OpenBSD: Makefile,v 1.14 2011/06/02 13:41:36 ajacoutot Exp $
PKG_ARCH= *
@ -11,6 +11,8 @@ PKGNAME= architect-${V}
CATEGORIES= databases
WRKDIST= ${WRKDIR}/architect-${V}/
REVISION= 0
HOMEPAGE= http://www.sqlpower.ca/page/architect
MAINTAINER= Ian Darwin <ian@openbsd.org>

View File

@ -1,3 +1,9 @@
$OpenBSD: README,v 1.2 2011/06/02 13:41:36 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
To get started with SQL Power*Architect, please see the
Getting Started wiki page at
http://code.google.com/p/power-architect/wiki/GettingStarted
http://code.google.com/p/power-architect/wiki/GettingStarted

View File

@ -1,9 +1,9 @@
# $OpenBSD: Makefile,v 1.26 2010/11/23 18:14:19 jasper Exp $
# $OpenBSD: Makefile,v 1.27 2011/06/02 13:41:36 ajacoutot Exp $
COMMENT= GNU Problem Report Management System
DISTNAME= gnats-3.113.1
REVISION= 8
REVISION= 9
CATEGORIES= databases devel
MASTER_SITES= ${MASTER_SITE_GNU:=gnats/}

View File

@ -1,10 +1,11 @@
$OpenBSD: README,v 1.3 2010/11/23 18:14:19 jasper Exp $
$OpenBSD: README,v 1.4 2011/06/02 13:41:36 ajacoutot Exp $
Running GNATS on OpenBSD
========================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Post-installation steps:
------------------------
Post-installation steps
=======================
1. Add the following to /etc/services:
support 1529/tcp # GNATS
@ -46,6 +47,6 @@ increase privileges for all users of gnatsweb by changing 'view' to
'edit', or for individual users by adding rules to
${TRUEPREFIX}/share/gnats/gnats-db/gnats-adm/gnatsd.access.
References:
-----------
References
==========
Additional documentation at http://sunsite.ualberta.ca/Documentation/Gnu/gnats-3.113/

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.191 2011/05/27 21:07:00 sthen Exp $
# $OpenBSD: Makefile,v 1.192 2011/06/02 13:41:36 ajacoutot Exp $
SHARED_ONLY= Yes
@ -11,7 +11,7 @@ DISTNAME= mysql-${VERSION}
PKGNAME-main= mysql-client-${VERSION}
REVISION-main= 0
PKGNAME-server= mysql-server-${VERSION}
REVISION-server=7
REVISION-server=8
PKGNAME-tests= mysql-tests-${VERSION}
CATEGORIES= databases
V= MySQL-5.1

View File

@ -1,7 +1,8 @@
$OpenBSD: README-server,v 1.2 2011/01/04 16:03:00 ajacoutot Exp $
$OpenBSD: README-server,v 1.3 2011/06/02 13:41:37 ajacoutot Exp $
Using MySQL in an OpenBSD environment
=====================================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
If you are installing MySQL for the first time, you have to create
a default database first. In order to create the database, please run

View File

@ -1,9 +1,9 @@
# $OpenBSD: Makefile,v 1.11 2011/05/11 06:26:03 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.12 2011/06/02 13:41:37 ajacoutot Exp $
COMMENT = lightweight connection pooler for PostgreSQL
DISTNAME = pgbouncer-1.3.4
REVISION = 2
REVISION = 3
CATEGORIES = databases

View File

@ -1,10 +1,11 @@
$OpenBSD: README,v 1.3 2011/01/04 14:54:28 pea Exp $
$OpenBSD: README,v 1.4 2011/06/02 13:41:38 ajacoutot Exp $
Running pgbouncer on OpenBSD
============================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Post-installation steps:
------------------------
Post-installation steps
=======================
1. Carefully edit ${SYSCONFDIR}/pgbouncer/pgbouncer.ini and
${SYSCONFDIR}/pgbouncer/userlist.txt to fit your needs.
@ -16,6 +17,6 @@ Post-installation steps:
3. Launch pgbouncer with /etc/rc.d/pgbouncer start
Random hints:
-------------
Random hints
============
Check /var/log/pgbouncer/pgbouncer.log if something goes wrong.

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.151 2011/05/08 23:11:36 fgsch Exp $
# $OpenBSD: Makefile,v 1.152 2011/06/02 13:41:38 ajacoutot Exp $
COMMENT-main= PostgreSQL RDBMS (client)
COMMENT-server= PostgreSQL RDBMS (server)
@ -12,6 +12,7 @@ PKGNAME-server= postgresql-server-${VERSION}
PKGNAME-docs= postgresql-docs-${VERSION}
PKGNAME-contrib=postgresql-contrib-${VERSION}
REVISION-server=0
CATEGORIES= databases
SHARED_LIBS= ecpg 7.2 \

View File

@ -1,7 +1,8 @@
$OpenBSD: README-server,v 1.5 2011/04/07 14:45:26 pea Exp $
$OpenBSD: README-server,v 1.6 2011/06/02 13:41:38 ajacoutot Exp $
Using PostgreSQL in an OpenBSD environment
==========================================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
At least two different accounts are involved when working with PostgreSQL:
One is an OpenBSD userid, '_postgresql', which is used as the userid of files
@ -100,7 +101,6 @@ To generate the keytab:
Upgrade Howto (for a major upgrade)
===================================
If you didn't install PostgreSQL by following this README,
you must adapt these instructions to your setup.
@ -135,10 +135,8 @@ $ pg_ctl -D /var/postgresql/data -l /var/postgresql/logfile start
8) Restore your data:
$ psql -U postgres < /var/postgresql/full.sqldump
Clients/Frontends
=================
Many applications can use the PostgreSQL database right away. To facilitate
administration of a PostgreSQL database, two clients are notable:

View File

@ -1,10 +1,10 @@
# $OpenBSD: Makefile,v 1.15 2011/03/02 07:20:53 jasper Exp $
# $OpenBSD: Makefile,v 1.16 2011/06/02 13:41:38 ajacoutot Exp $
COMMENT= AVR microcontroller hardware in-system programmer
V= 5.10
DISTNAME= avrdude-${V}
REVISION= 1
REVISION= 2
DISTFILES+= avrdude-${V}.tar.gz avrdude-doc-${V}.pdf
CATEGORIES= devel

View File

@ -1,10 +1,11 @@
$OpenBSD: README,v 1.1 2010/12/12 20:20:56 jasper Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:38 ajacoutot Exp $
Running AVRDUDE on OpenBSD
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Programming Arduio devices
==========================
Programming Arduio devices:
---------------------------
If you're planning on programming *duino devices (with an FTDI chip)
using avrdude, you'll want to invoke it something like this:

View File

@ -1,10 +1,10 @@
# $OpenBSD: Makefile,v 1.41 2011/04/21 11:28:22 landry Exp $
# $OpenBSD: Makefile,v 1.42 2011/06/02 13:41:38 ajacoutot Exp $
# $FreeBSD: ports/devel/cvsweb/Makefile,v 1.28 2000/09/23 20:48:45 knu Exp $
COMMENT= WWW CGI script to browse CVS repository trees
DISTNAME= cvsweb-2.0.6
REVISION = 10
REVISION = 11
CATEGORIES= devel www
HOMEPAGE= http://www.freebsd.org/projects/cvsweb.html

View File

@ -1,4 +1,8 @@
$OpenBSD: README,v 1.2 2011/04/21 11:28:22 landry Exp $
$OpenBSD: README,v 1.3 2011/06/02 13:41:38 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
# Author: Jolan Luff <jolan@openbsd.org>

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.76 2011/04/29 11:09:10 stsp Exp $
# $OpenBSD: Makefile,v 1.77 2011/06/02 13:41:38 ajacoutot Exp $
COMMENT-main = GIT - Tree History Storage Tool
COMMENT-svn = GIT - subversion interoperability tools
@ -11,6 +11,8 @@ PKGNAME-svn = git-svn-${V}
PKGNAME-x11 = git-x11-${V}
CATEGORIES = devel
REVISION-main= 0
HOMEPAGE = http://git-scm.com/
MAINTAINER = Bernd Ahlers <bernd@openbsd.org>

View File

@ -1,9 +1,11 @@
$OpenBSD: README-main,v 1.1 2010/11/05 08:23:04 bernd Exp $
$OpenBSD: README-main,v 1.2 2011/06/02 13:41:38 ajacoutot Exp $
Some notes on using git in an OpenBSD environment.
* git send-email
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
git send-email
==============
To make it work with SSL/TLS and SMTP auth you have to install
the following additional packages.

View File

@ -1,10 +1,10 @@
# $OpenBSD: Makefile,v 1.9 2010/11/15 19:45:59 espie Exp $
# $OpenBSD: Makefile,v 1.10 2011/06/02 13:41:38 ajacoutot Exp $
COMMENT = continuous integration server
VERSION = 1.365
DISTNAME = hudson # nonsensical versioning, alas.
REVISION = 0
REVISION = 1
PKGNAME = hudson-${VERSION}
DIST_SUBDIR = hudson-${VERSION}

View File

@ -1,6 +1,8 @@
$OpenBSD: README,v 1.1 2010/11/09 21:39:57 jasper Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:38 ajacoutot Exp $
Running Hudson on OpenBSD.
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
To arrange for the standalone Hudson server to run automatically
on reboot, add the following to /etc/rc.local:

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.10 2010/11/22 14:07:54 jasper Exp $
# $OpenBSD: Makefile,v 1.11 2011/06/02 13:41:38 ajacoutot Exp $
SHARED_ONLY= Yes
@ -9,6 +9,8 @@ DISTNAME= ideaIC-${V}
PKGNAME= intellij-${V}
CATEGORIES= java devel
REVISION= 0
HOMEPAGE= http://www.jetbrains.com/idea/
MAINTAINER= Daniel Dickman <didickman@gmail.com>

View File

@ -1,17 +1,16 @@
$OpenBSD: README,v 1.1 2010/11/10 07:58:59 jasper Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:38 ajacoutot Exp $
IntelliJ on OpenBSD
===================
1. Windowing Problems
---------------------
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Windowing Problems
==================
If the splash-screen displays but you then only see a grey main screen,
install the wmname package and run 'wmname LG3D'. This is a problem that
has been seen with some Java-based applications used with a non-reparenting
window manager (e.g. cwm).
2. Native Libraries
-------------------
Native Libraries
================
Functionality depending on native libraries is not likely to work.

View File

@ -1,9 +1,9 @@
# $OpenBSD: Makefile,v 1.4 2011/05/11 06:22:17 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.5 2011/06/02 13:41:38 ajacoutot Exp $
COMMENT = continuous integration server
VERSION = 1.401
REVISION = 2
REVISION = 3
DISTNAME = jenkins
PKGNAME = jenkins-${VERSION}
DIST_SUBDIR = jenkins-${VERSION}

View File

@ -1,6 +1,8 @@
$OpenBSD: README,v 1.2 2011/03/28 22:03:44 ian Exp $
$OpenBSD: README,v 1.3 2011/06/02 13:41:38 ajacoutot Exp $
Running Jenkins on OpenBSD.
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
To arrange for the standalone Jenkins server to run automatically
on reboot, add "jenkins" to "rc_scripts" in /etc/rc.conf.local, e.g.:

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.19 2011/05/11 06:22:17 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.20 2011/06/02 13:41:38 ajacoutot Exp $
SHARED_ONLY= Yes
@ -7,7 +7,7 @@ COMMENT= NetBeans Java IDE
V= 6.9.1
DISTNAME= netbeans-${V}
CATEGORIES= java devel
REVISION= 0
REVISION= 1
HOMEPAGE= http://www.netbeans.org/

View File

@ -1,10 +1,11 @@
$OpenBSD: README,v 1.1 2010/11/12 12:26:16 jasper Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:38 ajacoutot Exp $
NetBeans 6.8 on OpenBSD
=======================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
1. Help System
--------------
Help System
===========
NetBeans relies on the presence of a firefox binary for access to
the online help system. Firefox is not set up as a runtime dependency
@ -18,8 +19,8 @@ ln -s ${LOCALBASE}/bin/firefox35 ${LOCALBASE}/bin/firefox
You can also customize this setting within the IDE by going to
Tools> Options> General> Web Browser.
2. Font issues in the output window
-----------------------------------
Font issues in the output window
================================
After hitting the Clean & Build or the Run buttons from
within the IDE, the output window will show square boxes
@ -28,8 +29,8 @@ instead of fonts.
Bug 145696 was filed but marked as WONTFIX by NetBeans developers:
https://netbeans.org/bugzilla/show_bug.cgi?id=145696
3. Native Libraries
-------------------
Native Libraries
================
The profiler module is not included in the port. Additionally,
the following modules, although included, contain native code which

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.11 2011/04/21 10:20:43 eric Exp $
# $OpenBSD: Makefile,v 1.12 2011/06/02 13:41:38 ajacoutot Exp $
COMMENT = system to automate the compile/test cycle
@ -6,6 +6,8 @@ MODPY_EGG_VERSION = 0.8.3p1
DISTNAME = buildbot-${MODPY_EGG_VERSION}
PKGNAME = py-${DISTNAME:S/p/./}
REVISION = 0
CATEGORIES = devel
HOMEPAGE = http://buildbot.net/

View File

@ -1,7 +1,8 @@
$OpenBSD: README,v 1.1 2011/04/21 10:20:43 eric Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:38 ajacoutot Exp $
Using BuildBot master in an OpenBSD environment
===============================================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
On OpenBSD, the BuildBot package has an associated _buildbot user for
running the master. The default master directory is expected to be

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.3 2011/04/24 19:15:13 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.4 2011/06/02 13:41:38 ajacoutot Exp $
COMMENT= buildslave implementation for the buildot system
@ -6,7 +6,7 @@ MODPY_EGG_VERSION= 0.8.3
DISTNAME= buildbot-slave-${MODPY_EGG_VERSION}
PKGNAME= py-buildslave-${MODPY_EGG_VERSION}
REVISION= 0
REVISION= 1
CATEGORIES= devel

View File

@ -1,7 +1,8 @@
$OpenBSD: README,v 1.1 2011/04/21 10:22:38 eric Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:38 ajacoutot Exp $
Using BuildBot slave in an OpenBSD environment
==============================================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
On OpenBSD, the BuildBot package has an associated _buildslave user
for running the slave. The default slave directory is expected to be

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.14 2011/05/19 18:35:43 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.15 2011/06/02 13:41:38 ajacoutot Exp $
# XXX Are we affected by CVE-2008-0386? Our sed(1) does not behave as
# the GNU version.
@ -8,7 +8,7 @@ COMMENT= utilities to assist desktop integration tasks
DISTNAME= xdg-utils-1.0.2
CATEGORIES= devel
REVISION= 11
REVISION= 12
HOMEPAGE= http://portland.freedesktop.org/wiki/

View File

@ -1,4 +1,8 @@
$OpenBSD: README,v 1.1 2010/11/06 08:03:05 ajacoutot Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:38 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
xdg-utils is patched to permit customized start scripts when opening
files, URLs or emails. Example scripts can be found in

View File

@ -1,8 +1,8 @@
# $OpenBSD: Makefile,v 1.19 2011/01/15 01:09:43 naddy Exp $
# $OpenBSD: Makefile,v 1.20 2011/06/02 13:41:38 ajacoutot Exp $
BRANCH= 21.4
VERSION= 22
REVISION = 2
REVISION = 3
WANTLIB= c m ncurses util

View File

@ -1,10 +1,11 @@
$OpenBSD: README,v 1.1 2011/01/03 10:44:27 jasper Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:38 ajacoutot Exp $
Running XEmacs on OpenBSD
==============================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Installing modules:
-------------------
Installing modules
==================
XEmacs is pretty useless as-is. It is just an engine.
You need to install modules to provide your users full functionality.
There are two methods to achieve this:

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.14 2011/05/09 15:54:56 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.15 2011/06/02 13:41:38 ajacoutot Exp $
# no success building on other archs yet
ONLY_FOR_ARCHS= amd64 i386 powerpc
@ -6,7 +6,7 @@ ONLY_FOR_ARCHS= amd64 i386 powerpc
COMMENT= multi system emulator
DISTNAME= qemu-0.9.1
REVISION= 19
REVISION= 20
CATEGORIES= emulators
HOMEPAGE= http://www.nongnu.org/qemu/

View File

@ -1,7 +1,8 @@
$OpenBSD: README,v 1.3 2011/05/09 15:54:56 ajacoutot Exp $
$OpenBSD: README,v 1.4 2011/06/02 13:41:38 ajacoutot Exp $
README for OpenBSD users
------------------------
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
==> Quick Start

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.68 2011/05/25 07:43:48 sthen Exp $
# $OpenBSD: Makefile,v 1.69 2011/06/02 13:41:38 ajacoutot Exp $
# no success building on other archs yet
ONLY_FOR_ARCHS = amd64 i386 mips64 mips64el powerpc sparc64
@ -7,7 +7,7 @@ VMEM_WARNING = yes
COMMENT = multi system emulator
DISTNAME = qemu-0.14.1
REVISION = 0
REVISION = 1
CATEGORIES = emulators
MASTER_SITES = ${MASTER_SITE_SAVANNAH:=qemu/}

View File

@ -1,7 +1,8 @@
$OpenBSD: README,v 1.4 2011/05/09 15:54:56 ajacoutot Exp $
$OpenBSD: README,v 1.5 2011/06/02 13:41:38 ajacoutot Exp $
README for OpenBSD users
------------------------
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
==> Quick Start

View File

@ -1,9 +1,9 @@
# $OpenBSD: Makefile,v 1.3 2010/11/16 11:23:26 espie Exp $
# $OpenBSD: Makefile,v 1.4 2011/06/02 13:41:38 ajacoutot Exp $
COMMENT = commander keen clone
DISTNAME = clonekeen-src-84
PKGNAME = clonekeen-8.4
REVISION = 0
REVISION = 1
CATEGORIES = games
WRKDIST = ${WRKDIR}/keen

View File

@ -1,7 +1,8 @@
$OpenBSD: README,v 1.1 2010/11/07 18:58:39 jasper Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:38 ajacoutot Exp $
CloneKeen Game Data Install Instructions
========================================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
1) Go and download/buy commander keen for DOS and unzip it somewhere.
In this example we unzip in /tmp/dos.

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.18 2011/04/02 15:39:36 rpointel Exp $
# $OpenBSD: Makefile,v 1.19 2011/06/02 13:41:38 ajacoutot Exp $
COMMENT= open source clone of the game Transport Tycoon Deluxe
@ -11,6 +11,8 @@ MSX_V= 0.3.1
DISTFILES= ${DISTNAME}${EXTRACT_SUFX} \
opengfx-${GFX_V}.zip:0 opensfx-${SFX_V}.zip:1 openmsx-${MSX_V}.zip:2
REVISION= 0
CATEGORIES= games
HOMEPAGE= http://www.openttd.org/

View File

@ -1,7 +1,8 @@
$OpenBSD: README,v 1.1 2010/11/22 13:04:22 jasper Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:38 ajacoutot Exp $
Running OpenTTD on OpenBSD
==========================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
OpenTTD comes with free data and music. However, if you prefer to
play with the original Transport Tycoon Deluxe data files you can

View File

@ -1,10 +1,10 @@
# $OpenBSD: Makefile,v 1.43 2011/05/11 06:56:43 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.44 2011/06/02 13:41:38 ajacoutot Exp $
COMMENT= API for accessing scanners, backends
DISTNAME= sane-backends-1.0.22
REVISION= 3
REVISION= 4
SHARED_LIBS= sane 2.0 # .1.0
CATEGORIES= graphics

View File

@ -1,12 +1,13 @@
$OpenBSD: README,v 1.7 2011/03/09 13:05:20 ajacoutot Exp $
$OpenBSD: README,v 1.8 2011/06/02 13:41:38 ajacoutot Exp $
Using sane(7) under OpenBSD
===========================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
First read ${TRUEPREFIX}/share/doc/sane-backends/PROBLEMS.
USB
---
===
Since USB scanning will be handled by libusb, you need to allow the
_saned user access to the corresponding USB endpoint. To do so, find
where your scanner is attached to using `sudo usbdevs -vd` then change
@ -35,19 +36,19 @@ You can then grant users direct access to the scanner by adding them to
the _saned group.
SCSI
----
====
SANE only supports the generic SCSI uk(4) devices.
Make sure your user account has access to the scanner device node or you
will not be able to scan.
LOCKING
-------
=======
Some backends (like sane-plustek(5)) use a lockfile for allowing
multiple access to one scanner. If using such a backend, you must
add yourself to the _saned group or you will not be able to scan.
NETWORK
-------
=======
By default, the saned(8) daemon runs as _saned, so you need to allow the
_saned user access to the scanner device node.
If you're planning on using the SANE network daemon (saned) with

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.12 2010/11/17 08:05:16 espie Exp $
# $OpenBSD: Makefile,v 1.13 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT-main= OCR Engine developed at HP Labs
@ -7,7 +7,7 @@ DISTNAME= tesseract-${V}
CATEGORIES= graphics textproc
PKGNAME-main= ${DISTNAME}
REVISION-main= 2
REVISION-main= 3
SHARED_LIBS += tesseract_api 0.0 # 3.0
SHARED_LIBS += tesseract_ccstruct 0.0 # 3.0

View File

@ -1,7 +1,8 @@
$OpenBSD: README-main,v 1.1 2010/11/07 18:49:10 jasper Exp $
$OpenBSD: README-main,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
OCR with tesseract under OpenBSD
================================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Here's a quick HOWTO about optical character recognition using:
scanimage(1) -- from the sane-backends package

View File

@ -1,11 +1,11 @@
# $OpenBSD: Makefile,v 1.16 2011/05/14 21:29:03 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.17 2011/06/02 13:41:39 ajacoutot Exp $
SHARED_ONLY = Yes
COMMENT = intelligent input bus framework
DISTNAME = ibus-1.3.9
REVISION = 3
REVISION = 4
SHARED_LIBS = ibus 1.0 # 2.0

View File

@ -1,4 +1,8 @@
$OpenBSD: README,v 1.2 2010/11/11 09:42:11 fgsch Exp $
$OpenBSD: README,v 1.3 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
To make IBus work when X is started add the following lines to
~/.xinitrc or ~/.xsession:

View File

@ -1,11 +1,11 @@
# $OpenBSD: Makefile,v 1.15 2010/11/17 08:05:17 espie Exp $
# $OpenBSD: Makefile,v 1.16 2011/06/02 13:41:39 ajacoutot Exp $
SHARED_ONLY = Yes
COMMENT = smart common input method platform
DISTNAME = scim-1.4.9
REVISION = 8
REVISION = 9
SHARED_LIBS += scim-1.0 0.0 # .10.4
SHARED_LIBS += scim-x11utils-1.0 0.0 # .10.4

View File

@ -1,4 +1,8 @@
$OpenBSD: README,v 1.1 2010/11/08 09:00:20 fgsch Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
To make SCIM work when X is started add the following lines to
~/.xinitrc or ~/.xsession:

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.15 2011/01/05 16:13:53 stu Exp $
# $OpenBSD: Makefile,v 1.16 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT = Tool Command Language
@ -8,6 +8,7 @@ SHARED_LIBS = tcl85 0.6
CATEGORIES = lang lang/tcl
HOMEPAGE = http://www.tcl.tk/
MAINTAINER = Stuart Cassoff <stwo@users.sourceforge.net>
REVISION = 0
# BSD
PERMIT_PACKAGE_CDROM = Yes

View File

@ -1,4 +1,8 @@
# $OpenBSD: README,v 1.2 2011/01/05 16:13:53 stu Exp $
# $OpenBSD: README,v 1.3 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
cat << "EOTEXT" > /dev/null

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.16 2010/11/19 07:23:05 espie Exp $
# $OpenBSD: Makefile,v 1.17 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT-main= UW e-mail client
COMMENT-pico= UW text editor
@ -18,7 +18,7 @@ PKGNAME-main= alpine-${V}
PKGNAME-pico= pico-${PICO_V}
PKGNAME-pilot= pilot-${PILOT_V}
REVISION-main= 3
REVISION-main= 4
REVISION-pico= 1
REVISION-pilot= 3

View File

@ -1,14 +1,14 @@
$OpenBSD: README-main,v 1.1 2010/11/12 13:54:47 jasper Exp $
$OpenBSD: README-main,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
Alpine Quick Start: sending and receiving mail
==============================================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Below is a quick start guide to show how to set up Alpine to use IMAP or
POP3 for accessing your email and SMTP for sending email.
IMAP
----
====
1. Make sure your email provider has IMAP support enabled (some
providers require you to explicitly enable IMAP support).
@ -33,9 +33,8 @@ As a concrete example, here's how this would look for gmail:
4. Press Ctrl-X to exit and save, enter your password when prompted and
(E)xit back to the main screen.
POP3
----
====
1. Follow the same instructions as above for IMAP, except for step 3
Use the following:
@ -52,9 +51,8 @@ where:
As a concrete example, here's how this would look for gmail:
pop.gmail.com:995/novalidate-cert/user=yourname@gmail.com/pop3/ssl
SMTP
----
====
1. Make sure you are back at alpine's main screen.

View File

@ -1,9 +1,9 @@
# $OpenBSD: Makefile,v 1.9 2011/05/11 12:57:47 jasper Exp $
# $OpenBSD: Makefile,v 1.10 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT = mail server storing messages in a database
DISTNAME = archiveopteryx-3.1.3
REVISION = 5
REVISION = 6
CATEGORIES = mail databases
HOMEPAGE = http://www.archiveopteryx.org/

View File

@ -1,7 +1,8 @@
$OpenBSD: README,v 1.1.1.1 2011/01/09 09:36:21 landry Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
Running Archiveopteryx on OpenBSD
=================================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Archiveopteryx is now installed, and sample configuration files were
created in ${SYSCONFDIR}/archiveopteryx.conf and ${SYSCONFDIR}/aoxsuper.conf
@ -10,8 +11,8 @@ Before using it, you will need to create PostgreSQL users and database,
and you'll need to set aox db user password in archiveopteryx.conf,
and aoxsuper db user password in aoxsuper.conf.
Database initialisation:
------------------------
Database initialisation
=======================
Assuming you have an administrative account named `postgres',
you can create the aox/aoxsuper users and archiveopteryx database like
this:
@ -42,9 +43,8 @@ If performing an upgrade, you might need to update schema with:
aox upgrade schema
Certificate generation:
-----------------------
Certificate generation
======================
By default, archiveopteryx uses TLS (unless use-tls is set to no), so it
needs an ssl certificate file in /etc/ssl/archiveopteryx.pem containing
both private key and signed certificate to function properly. If you
@ -56,9 +56,8 @@ openssl req -config /etc/ssl/archiveopteryx-openssl.conf -x509 -days \
1764 -newkey rsa -nodes -keyout /etc/ssl/archiveopteryx.pem \
-out /etc/ssl/archiveopteryx.pem
Startup/Shutdown configuration:
-------------------------------
Startup/Shutdown configuration
==============================
Make sure to startup archiveopteryx after your DB server.
aox show status can give you the status of processes.

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.56 2011/04/13 15:18:23 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.57 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT-main= Cyrus IMAP server
COMMENT-perl= perl utils for the Cyrus IMAP server
@ -9,6 +9,8 @@ PKGNAME-main= ${DISTNAME}
FULLPKGNAME-perl=cyrus-imapd-perl-${V}
FULLPKGPATH-perl=mail/cyrus-imapd,-perl
REVISION-main= 0
CATEGORIES= mail
HOMEPAGE= http://www.cyrusimap.org/

View File

@ -1,7 +1,8 @@
$OpenBSD: README-main,v 1.1 2010/12/12 11:52:30 ajacoutot Exp $
$OpenBSD: README-main,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
Running cyrus-imapd under OpenBSD
=================================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
WARNING: mmap(2) is not fully POSIX on OpenBSD so cyrus needs to
map_refresh on every lock which will incure a performance penalty under

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.67 2010/11/06 08:32:42 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.68 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT-server= University of Washington IMAP4rev1/POP2/POP3 mail servers
COMMENT-mailutil=University of Washington IMAP4rev1/POP2/POP3 mail utility
@ -11,7 +11,7 @@ PKGNAME-server= imap-uw-${V}
PKGNAME-mailutil=mailutil-uw-${V}
PKGNAME-c-client=c-client-${V}
REVISION-server= 3
REVISION-server= 4
REVISION-mailutil= 1
REVISION-c-client= 1

View File

@ -1,4 +1,8 @@
$OpenBSD: README-server,v 1.1 2010/11/06 08:14:37 ajacoutot Exp $
$OpenBSD: README-server,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
The ipop2d, ipop3d, and imapd daemons should be invoked by your
/etc/inetd.conf file with lines such as:

View File

@ -1,9 +1,9 @@
# $OpenBSD: Makefile,v 1.67 2011/05/11 12:57:48 jasper Exp $
# $OpenBSD: Makefile,v 1.68 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT= mailing list manager with web interface
DISTNAME= mailman-2.1.14
REVISION= 10
REVISION= 11
CATEGORIES= mail www
HOMEPAGE= http://www.gnu.org/software/mailman/

View File

@ -1,4 +1,8 @@
$OpenBSD: README,v 1.2 2010/11/10 07:36:44 ajacoutot Exp $
$OpenBSD: README,v 1.3 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Throughout this document $mailmandir is the directory mailman is installed
in. This defaults to ${TRUEPREFIX}/lib/mailman. Most of this text is

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.41 2011/05/12 12:20:41 sthen Exp $
# $OpenBSD: Makefile,v 1.42 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT= virus/spam scanning framework
@ -11,6 +11,7 @@ DISTNAME= mailscanner-${V}.${Vss}
PKGNAME= mailscanner-${V}.${Vss:S/-/./}
DISTFILES= MailScanner-install-${V}.${Vss}${EXTRACT_SUFX}
WRKDIST= ${WRKDIR}/MailScanner-${V}.${Vss}
REVISION= 0
HOMEPAGE= http://www.mailscanner.info/

View File

@ -1,4 +1,8 @@
$OpenBSD: README,v 1.1 2010/11/16 09:17:55 jasper Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
The MailScanner port is using the original MailScanner tarball from
www.mailscanner.info. This tarball puts all the MailScanner files in

View File

@ -1,9 +1,9 @@
# $OpenBSD: Makefile,v 1.20 2011/05/11 12:57:48 jasper Exp $
# $OpenBSD: Makefile,v 1.21 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT= mailfilter to identify and mark spam
DISTNAME= mimedefang-2.71
REVISION= 4
REVISION= 5
CATEGORIES= mail
HOMEPAGE= http://www.mimedefang.org/

View File

@ -1,10 +1,11 @@
$OpenBSD: README,v 1.1 2010/12/07 02:56:19 okan Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
Running MIMEDEFANG on OpenBSD
=============================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
1. Post-installation steps:
---------------------------
Post-installation steps
=======================
Register the mimedefang milter with sendmail(8) by adding the following
to your .mc file:
@ -14,7 +15,7 @@ to your .mc file:
Then re-generate your .cf file.
2. Start-up order:
------------------
Start-up order
==============
Be sure to start mimedefang_multiplexor before mimedefang_daemon in
rc.local(8).

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.12 2010/11/19 07:23:07 espie Exp $
# $OpenBSD: Makefile,v 1.13 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT-main= accept email on behalf of real sendmail
COMMENT-chroot= static mini_sendmail for chrooted apache
@ -6,7 +6,7 @@ COMMENT-chroot= static mini_sendmail for chrooted apache
V= 1.3.6
DISTNAME= mini_sendmail-${V}
PKGNAME-main= mini_sendmail-${V}
REVISION-main= 1
REVISION-main= 2
PKGNAME-chroot= mini_sendmail-chroot-${V}
REVISION-chroot=1
CATEGORIES= mail www

View File

@ -1,4 +1,8 @@
$OpenBSD: README-main,v 1.1 2010/11/15 18:18:55 jasper Exp $
$OpenBSD: README-main,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
First things first, we need to install the chroot subpackage of
mini_sendmail if you have not done so already. This will put a

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.122 2011/04/29 08:01:26 landry Exp $
# $OpenBSD: Makefile,v 1.123 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT-main = Mozilla e-mail, rss and usenet client
COMMENT-lightning = Mozilla Thunderbird calendar extension
@ -13,6 +13,7 @@ MOZILLA_CODENAME = mail
MULTI_PACKAGES = -main -lightning
PKGNAME-main = ${PKGNAME}
REVISION-main = 0
PKGNAME-lightning = lightning-1.0beta2
EPOCH-lightning = 0
REVISION-lightning = 16

View File

@ -1,4 +1,8 @@
$OpenBSD: README-main,v 1.1 2010/11/11 09:30:36 jasper Exp $
$OpenBSD: README-main,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
If you encounter strange problems or Thunderbird doesn't start at
all, try the -safe-mode switch.
@ -6,7 +10,7 @@ all, try the -safe-mode switch.
To disable anti-aliasing (xft) set GDK_USE_XFT=0 in the environment.
Links
=====
To make Thunderbird open links using Firefox, shut down Thunderbird
and add these lines to ~/.thunderbird/<something>.default/prefs.js:
@ -15,7 +19,7 @@ user_pref("network.protocol-handler.app.http", "${LOCALBASE}/bin/firefox");
user_pref("network.protocol-handler.app.https", "${LOCALBASE}/bin/firefox");
Plugins
=======
Thunderbird looks for plugins in ~/.mozilla/plugins
${TRUEPREFIX}/mozilla-thunderbird/plugins and
${LOCALBASE}/lib/mozilla/plugins.
@ -23,7 +27,7 @@ If the environment variable MOZ_PLUGIN_PATH is specified, this
location will be overridden.
Debugging
=========
If you encounter crashes, you might want to build the debug FLAVOR of
this package, and run 'thunderbird -g' to run thunderbird inside gdb, so
that you can gather debugging logs and traces.

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.11 2011/05/05 13:37:04 gsoares Exp $
# $OpenBSD: Makefile,v 1.12 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT= automatically fetch hotmail.com email
@ -7,6 +7,7 @@ PKGNAME= p5-GetLive-2.3
PKG_ARCH= *
CATEGORIES= mail perl5
EXTRACT_SUFX= .tgz
REVISION= 0
MAINTAINER= Michael Erdely <merdely@openbsd.org>

View File

@ -1,7 +1,8 @@
$OpenBSD: README,v 1.1 2011/05/05 13:37:04 gsoares Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
Running p5-GetLive on OpenBSD
=============================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Refer to ${PREFIX}/share/doc/GetLive/Manual for configuration file
options.

View File

@ -1,11 +1,11 @@
# $OpenBSD: Makefile,v 1.14 2011/05/11 12:57:48 jasper Exp $
# $OpenBSD: Makefile,v 1.15 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT = mailing list manager with web interface
VERSION = 6.1.3
DISTNAME = sympa-${VERSION}
REVISION = 3
REVISION = 4
CATEGORIES = mail www

View File

@ -1,4 +1,8 @@
$OpenBSD: README,v 1.3 2010/12/30 17:51:25 landry Exp $
$OpenBSD: README,v 1.4 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
SYMPA is now installed, and sample configuration files were created in
${SYMPA_HOME}/${SYSCONFDIR}/sympa.conf and ${SYMPA_HOME}/${SYSCONFDIR}/wwsympa.conf

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.81 2011/06/02 12:46:37 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.82 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT-main= MS Exchange groupware suite replacement
COMMENT-web= zarafa webaccess frontend and MAPI extensions for PHP
@ -7,6 +7,8 @@ PKGNAME= zarafa-${V}
PKGNAME-main= zarafa-${V}
PKGNAME-web= zarafa-webaccess-${V}
REVISION-main= 0
CATEGORIES= mail www productivity
SHARED_LIBS += mapi 2.0 # 0.0

View File

@ -1,24 +1,22 @@
$OpenBSD: README-main,v 1.7 2011/06/02 12:46:37 ajacoutot Exp $
$OpenBSD: README-main,v 1.8 2011/06/02 13:41:39 ajacoutot Exp $
Running zarafa on OpenBSD
=========================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
*** Upgrading users: refer to zarafa documentation on the web to check
*** if any particular step is required after upgrading to a new version.
6.40 -> 7.0 upgrade
-------------------
===================
See http://doc.zarafa.com/trunk/Release_Notes/en-US/html/_upgrading_to_zcp_7_0.html
The zarafa7-upgrade script is available at:
${TRUEPREFIX}/share/doc/zarafa/zarafa7-upgrade
Note that this script requires the py-mysql package.
Post-install/update instructions for Zarafa
-------------------------------------------
===========================================
By default the server is configured to accept SOAP connections on port
236. If you wish to connect Outlook clients on port 80, please setup
your web server to proxy HTTP requests with URI=/zarafa to
@ -28,28 +26,22 @@ It is advised to tune the MySQL installation according to:
http://zarafa.com/wiki/index.php/MySQL_tuning
(especially for max_allowed_packet)
Before Starting zarafa-server for the first time
------------------------------------------------
* a MySQL datatabase access needs to be configured in
================================================
A MySQL datatabase access needs to be configured in
${SYSCONFDIR}/zarafa/server.cfg
After zarafa-server was started for the first time
--------------------------------------------------
* Creating the public store.
==================================================
Creating the public store.
# ${TRUEPREFIX}/bin/zarafa-admin -s
* Adding an admin user -- see zarafa-admin(1).
Adding an admin user -- see zarafa-admin(1).
# ${TRUEPREFIX}/bin/zarafa-admin -c zadmin -p secret \
-e zarafa.admin@domain.tld -f "John Doe" -a 2
Mail delivery agent configuration
---------------------------------
=================================
The easiest way to use zarafa-dagent system-wide under a stock OpenBSD
sendmail(8) installation is to use procmail(1).
See the following URL for other MTA integration:
@ -91,10 +83,8 @@ to
The .forward will be automatically generated when a new user is added to
Zarafa.
Zarafa webaccess
----------------
================
Zarafa webaccess is installed under
${INSTDIR}
@ -120,10 +110,8 @@ ${PREFIX-web}/conf/php5/${MODULE_NAME}.ini:
# ln -fs ${PREFIX-web}/conf/php5.sample/${MODULE_NAME}.ini \
${PREFIX-web}/conf/php5/${MODULE_NAME}.ini
The PHP mapi module and OpenBSD Apache
--------------------------------------
======================================
When using the OpenBSD Apache server, the runtime loader will need to
pre-load the pthread shared library. While the php binary is linked with
-pthread, httpd is not and the PHP mapi module needs
@ -136,10 +124,8 @@ rm -f /var/www/logs/{ssl_mutex,httpd.lock,accept.lock}.*
echo 'starting httpd'
LANG=en_US.UTF-8 LD_PRELOAD=/usr/lib/libpthread.so /usr/sbin/httpd -DSSL
Documentation and help
----------------------
======================
Each zarafa-* command has its corresponding manpage.
Some documentation is also available on the Internet:

View File

@ -1,15 +1,17 @@
# $OpenBSD: Makefile,v 1.33 2010/11/19 22:31:32 espie Exp $
# $OpenBSD: Makefile,v 1.34 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT-main= cooperative file distribution system implemented in Python
COMMENT-gui= graphical interface components for BitTorrent
VERSION= 4.4.0
DISTNAME= BitTorrent-${VERSION}
REVISION= 8
PKGNAME-main= ${DISTNAME}
PKGNAME-gui= BitTorrent-gui-${VERSION}
CATEGORIES= net
REVISION-main= 9
REVISION-gui= 8
HOMEPAGE= http://www.bittorrent.com/
# Custom

View File

@ -1,4 +1,8 @@
$OpenBSD: README-main,v 1.1 2010/11/09 19:46:52 jasper Exp $
$OpenBSD: README-main,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
To begin using BitTorrent quickly, simply fetch a torrent file and
run bittorrent (X11) or bittorrent-curses:

View File

@ -1,9 +1,10 @@
# $OpenBSD: Makefile,v 1.17 2011/04/18 16:36:59 ajacoutot Exp $
# $OpenBSD: Makefile,v 1.18 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT= DNS relay for ad blocking
DISTNAME= adsuck-2.3
CATEGORIES= net
REVISION= 0
HOMEPAGE= http://opensource.conformal.com/wiki/Adsuck
MAINTAINER= Gonzalo L. R. <gonzalo@x61.com.ar>

View File

@ -1,10 +1,11 @@
$OpenBSD: README,v 1.3 2011/04/18 16:36:59 ajacoutot Exp $
$OpenBSD: README,v 1.4 2011/06/02 13:41:39 ajacoutot Exp $
Running adsuck on OpenBSD
=========================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Running adsuck(1) locally with dhclient(8)
------------------------------------------
==========================================
To make dhclient(8) play nice with adsuck(1), the following script has
been installed:

View File

@ -1,9 +1,10 @@
# $OpenBSD: Makefile,v 1.24 2010/12/23 22:54:39 jasper Exp $
# $OpenBSD: Makefile,v 1.25 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT= jabber server written in Erlang
V= 2.1.6
DISTNAME= ejabberd-$V
REVISION= 0
CATEGORIES= net

View File

@ -1,4 +1,8 @@
$OpenBSD: README,v 1.3 2010/11/06 07:56:48 ajacoutot Exp $
$OpenBSD: README,v 1.4 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
* Migration
When moving database between machines, or upgrading from 1.1.x to

View File

@ -1,9 +1,9 @@
# $OpenBSD: Makefile,v 1.9 2010/11/19 22:31:33 espie Exp $
# $OpenBSD: Makefile,v 1.10 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT = flickr API library and utility
DISTNAME = flickcurl-1.14
REVISION = 1
REVISION = 2
SHARED_LIBS += flickcurl 1.0 # .1.0
CATEGORIES = net

View File

@ -1,4 +1,8 @@
$OpenBSD: README,v 1.1 2010/11/08 21:29:10 jasper Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
You will need to have a ~/.flickcurl.conf .

View File

@ -1,9 +1,9 @@
# $OpenBSD: Makefile,v 1.44 2011/01/16 19:53:17 naddy Exp $
# $OpenBSD: Makefile,v 1.45 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT= server for streaming various media formats
DISTNAME= icecast-2.3.2
REVISION= 5
REVISION= 6
CATEGORIES= net audio
HOMEPAGE= http://www.icecast.org/

View File

@ -1,4 +1,8 @@
$OpenBSD: README,v 1.1 2010/11/11 10:32:54 edd Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Icecast v2 is very versatile and can be used in many different
environments. A streaming service provider has different requirements

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.5 2011/05/11 13:57:41 sthen Exp $
# $OpenBSD: Makefile,v 1.6 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT-main = network monitoring system (improved fork of Nagios)
COMMENT-cgi = cgi scripts for Icinga (classic Nagios-style UI)
@ -11,6 +11,8 @@ PKGNAME-cgi = icinga-cgi-$V
PKGNAME-ido = icinga-idoutils-$V
PKGNAME-api = icinga-api-$V
REVISION-main = 0
MULTI_PACKAGES = -main -cgi -api -ido
PREFIX-cgi = /var/www
PREFIX-api = /var/www

View File

@ -1,10 +1,11 @@
$OpenBSD: README-main,v 1.1.1.1 2011/03/28 14:06:08 sthen Exp $
$OpenBSD: README-main,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
Running ICINGA on OpenBSD
=========================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Getting Started
---------------
===============
The main documentation for Icinga is provided in HTML format as part of
the icinga-cgi package, see /var/www/icinga-cgi/docs/en/index.html
@ -20,7 +21,7 @@ This will parse all configuration files and warn about any problems
which have been identified.
Chroot Considerations
---------------------
=====================
If using OpenBSD's default chroot environment for httpd, some files
will need to be moved inside the jail and symbolic links created:
@ -34,7 +35,7 @@ will need to be moved inside the jail and symbolic links created:
ln -s /var/www/var/log/icinga /var/log
Web User-Interfaces
-------------------
===================
Two web-based user interfaces are available for Icinga:
@ -62,7 +63,7 @@ You should then be able to access the web interface at
http://localhost/icinga/
Moving from Nagios
------------------
==================
The configuration format is compatible with Nagios. If you'd like
to move across with minimal changes, you can point Icinga at your

View File

@ -1,9 +1,10 @@
# $OpenBSD: Makefile,v 1.3 2011/03/31 10:25:25 sthen Exp $
# $OpenBSD: Makefile,v 1.4 2011/06/02 13:41:39 ajacoutot Exp $
# Work in progress. Not yet linked to the build.
COMMENT = web UI for icinga
DISTNAME = icinga-web-$V
REVISION = 0
BUILD_DEPENDS = icinga-api-$V:net/icinga/core,-api
RUN_DEPENDS = www/pear \

View File

@ -1,4 +1,8 @@
$OpenBSD: README,v 1.1.1.1 2011/03/28 14:06:08 sthen Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
SQL> GRANT USAGE ON *.* TO 'icinga_web'@'localhost' IDENTIFIED BY 'icinga_web';
SQL> GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, ALTER, INDEX ON icinga_web.* TO 'icinga_web'@'localhost';

View File

@ -1,11 +1,11 @@
# $OpenBSD: Makefile,v 1.6 2011/04/28 09:45:39 sthen Exp $
# $OpenBSD: Makefile,v 1.7 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT = Multicast router utilizing IGMP forwarding
VERSION = 0.1-beta2
DISTNAME = igmpproxy-src-${VERSION}
PKGNAME = igmpproxy-${VERSION:S/-beta/b/}
REVISION = 2
REVISION = 3
CATEGORIES = net
MASTER_SITES = ${MASTER_SITE_SOURCEFORGE:=igmpproxy/}

View File

@ -1,7 +1,8 @@
$OpenBSD: README,v 1.2 2010/12/27 13:51:31 jasper Exp $
$OpenBSD: README,v 1.3 2011/06/02 13:41:39 ajacoutot Exp $
Running igmpproxy on OpenBSD
-----------------------------
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
To use igmpproxy on OpenBSD, you will need to configure it by
editing ${SYSCONFDIR}/igmpproxy.conf, and configure the OS for

View File

@ -1,9 +1,9 @@
# $OpenBSD: Makefile,v 1.12 2011/04/14 12:55:38 pea Exp $
# $OpenBSD: Makefile,v 1.13 2011/06/02 13:41:39 ajacoutot Exp $
COMMENT = service monitoring daemon
DISTNAME = mon-${V}
REVISION = 7
REVISION = 8
WANTLIB = c

View File

@ -1,4 +1,8 @@
$OpenBSD: README,v 1.1 2010/11/10 13:54:56 pea Exp $
$OpenBSD: README,v 1.2 2011/06/02 13:41:39 ajacoutot Exp $
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
mon is a tool for monitoring the availability of services and sending alerts
on prescribed events.

View File

@ -1,4 +1,4 @@
# $OpenBSD: Makefile,v 1.30 2010/11/19 22:31:35 espie Exp $
# $OpenBSD: Makefile,v 1.31 2011/06/02 13:41:40 ajacoutot Exp $
COMMENT-main= nagios base plugins
COMMENT-fping= fping plugin
@ -23,7 +23,7 @@ PKGNAME-samba= nagios-plugins-samba-${V}
PKGNAME-snmp= nagios-plugins-snmp-${V}
CATEGORIES= net
REVISION-main= 0
REVISION-main= 1
HOMEPAGE= http://nagiosplug.sourceforge.net/

View File

@ -1,7 +1,8 @@
$OpenBSD: README-main,v 1.1 2010/11/15 09:56:53 sthen Exp $
$OpenBSD: README-main,v 1.2 2011/06/02 13:41:40 ajacoutot Exp $
Setting up Nagios' plugins on OpenBSD
-------------------------------------
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
The check_icmp and check_dhcp Nagios plugins need elevated privileges to
run properly. As the code quality of these plugins is not really good,

View File

@ -1,11 +1,11 @@
# $OpenBSD: Makefile,v 1.10 2011/05/11 12:03:19 jasper Exp $
# $OpenBSD: Makefile,v 1.11 2011/06/02 13:41:40 ajacoutot Exp $
MULTI_PACKAGES= -main -web
COMMENT-main= web-based front end for the nfdump netflow tools
COMMENT-web= html/php parts for nfsen
V= 1.3.5
REVISION-main= 2
REVISION-main= 3
DISTNAME= nfsen-$V
PKGNAME-main= ${DISTNAME}
PKGNAME-web= nfsen-web-$V

View File

@ -1,10 +1,11 @@
$OpenBSD: README-main,v 1.1 2011/03/24 23:04:00 sthen Exp $
$OpenBSD: README-main,v 1.2 2011/06/02 13:41:40 ajacoutot Exp $
Running NfSen on OpenBSD
========================
+-----------------------------------------------------------------------
| Running ${FULLPKGNAME} on OpenBSD
+-----------------------------------------------------------------------
Basic installation
------------------
==================
To proceed with an installation or upgrade, adjust ${SYSCONFDIR}/nfsen.conf
as required and run the configuration tool:
@ -19,7 +20,7 @@ http://nfsen.sourceforge.net/
Note, you may export netflow-compatible data from PF via pflow(4).
Chroot considerations
---------------------
=====================
NfSen is written with chroot in mind and is capable of communicating
with the main nfcap daemon running outside the jail. Adapting to this
configuration is a simple matter of moving a few files around (while
@ -30,7 +31,7 @@ the daemon is stopped).
# ln -s /var/www/var/db/nfsen /var/db/nfsen
PortTracker
-----------
===========
This optional module splits up traffic by port number. It can be useful
but is somewhat experimental. You can attempt to use it like this:

Some files were not shown because too many files have changed in this diff Show More