KAME-snap hacker's guide

$Id: hack.html,v 1.6 2006/04/11 08:01:14 kazu Exp $

Scope of the document

This document describes how you can:

obtaining releases

There are severay ways to obtain KAME snapshot kit.

ftp

(SNAP kit generated once a week, on mondays)
visit ftp://ftp.kame.net/pub/kame/snap/.

anonymous CVS

(always you can fetch the latest)
You can make your working directory in sync with the master repository, by using cvs with anonymous "pserver" connection. See the following files for complete description. There are mirror servers available:

cvsup

(always you can fetch the latest)
You can make your working directory in sync with the master repository, by using cvsup.

Install "cvsup" by using FreeBSD packages (binary package installation kit). Use the configuration file below, with some # sign edits:

To obtain the current snapshot, perform the following command:

% cvsup -g -L 2 kame-supfile
You can safely invoke the command from cron and similar tools.

For cvsup over socks, please see the separate page. There are mirror servers available:

cvsweb

You can browse KAME source code tree by using cvsweb interface. It is available at the following locations.

getting commit notifications

You can get commit notification emails by contacting majordomo@kame.net, with the following email content: Please DO NOT raise discussions on the above mailing lists. Discussions must be raised on snap-users mailing list, or on our bug database.

getting buildlab failure results

KAME project runs a facility called "build lab". At build lab, we compile KAME tree on various platforms, every 3 hours or so. You can get failure result notification by contacting majordomo@kame.net, with the following email content: Please DO NOT raise discussions on the above mailing lists. Discussions must be raised on snap-users mailing list, or on our bug database.

web resources to track the development


contributing the KAME project

Supplying bugfix patches.
Contributing new code modules.
To avoid legal matters, your source must obey the WIDE copyright notice, or more or less the same form such as Berkeley's, or maybe GPL2.
Making software packages into v6-ready form.
We are trying to collect v6-ready applications. It is recommended that you submit v6-ready application as a style of FreeBSD-ports.
For example, you can see kit/ports/sendmail6 in the current distribution kit.
Making drivers ready for IPv6 support.
Network interface card drivers need a small patch to become IPv6-ready. You can contribute by making the patch.
Provide developers with necessery hardwares.
let developers use your hardware for a while.
Give developers a feast (free lunch/dinner).

Comments should be shared among snap-users@kame.net.