head	1.4;
access;
symbols;
locks; strict;
comment	@# @;


1.4
date	2002.09.24.12.53.47;	author rse;	state Exp;
branches;
next	1.3;

1.3
date	2002.02.18.07.53.12;	author thl;	state Exp;
branches;
next	1.2;

1.2
date	2002.02.14.10.00.55;	author rse;	state Exp;
branches;
next	1.1;

1.1
date	2002.02.13.16.35.05;	author rse;	state Exp;
branches;
next	;


desc
@@


1.4
log
@update website, remove references to still not done areas, etc.
@
text
@
#use wml::ossp area=pkg

<title>Packages</title>

<subtitle>Package Sets</subtitle>

<h1>Package Sets</h1>

OSSP consists of a large set of packages (or components). They are split
into the following cathegories:

<h2>Tools</h2>

The tools OSSP provides are either developed for internal use in the
OSSP project environment or for the build process of the other OSSP
components. They are all small stand-alone applications and can be used
fully separately. 
[<a href="tool/">more</a>]
     
# <h2>Bootstrap</h2>
# 
# The bootstrap packages will be the necessary tools and libraries for
# bootstrapping the OSSP developer and end-user build environments.
# Currently this package category still does not exists. It will be
# created later by integrating packages from the <i>Tools</i> and
# <i>Libraries</i> cathegories.
# [<a href="boot/">more</a>]

<h2>Libraries</h2>

The libraries OSSP provides are the passive components used in the
OSSP platform. They are all stand-alone and fully reusable libraries
and can be used fully separately. On these packages currently the main
development effort is put, because they are the base of the whole OSSP
platform.
[<a href="lib/">more</a>]

# <h2>Kernel</h2>
# 
# The kernel packages will form the microkernel part of the OSSP platform.
# It will use the <i>Libraries</i> packages to provide the run-time
# environment for the <i>Modules</i> packages.
# [<a href="kern/">more</a>]
 
# <h2>Modules</h2>
# 
# The modules OSSP will be the active components used in the OSSP
# platform. They use the <i>Libraries</i> and the OSSP <i>Kernel</i>
# packages to provide the actual OSSP server functionality. They
# can be used only within the OSSP platform.
# [<a href="mod/">more</a>]
 
@


1.3
log
@typo
@
text
@d6 4
d21 8
a28 8
<h2>Bootstrap</h2>

The bootstrap packages will be the necessary tools and libraries for
bootstrapping the OSSP developer and end-user build environments.
Currently this package category still does not exists. It will be
created later by integrating packages from the <i>Tools</i> and
<i>Libraries</i> cathegories.
[<a href="boot/">more</a>]
d39 15
a53 15
<h2>Kernel</h2>

The kernel packages will form the microkernel part of the OSSP platform.
It will use the <i>Libraries</i> packages to provide the run-time
environment for the <i>Modules</i> packages.
[<a href="kern/">more</a>]

<h2>Modules</h2>

The modules OSSP will be the active components used in the OSSP
platform. They use the <i>Libraries</i> and the OSSP <i>Kernel</i>
packages to provide the actual OSSP server functionality. They
can be used only within the OSSP platform.
[<a href="mod/">more</a>]

@


1.2
log
@add more content to packages section
@
text
@d21 1
a21 1
Currently this package cathegory still does not exists. It will be
@


1.1
log
@Wohhoooo! First cut for our long awaited OSSP website...
@
text
@d6 44
@