Package Manager Design

Index: openacs-4/packages/acs-core-docs/www/apm-design.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/apm-design.html,v diff -u -N -r1.27.2.4 -r1.27.2.5 --- openacs-4/packages/acs-core-docs/www/apm-design.html 10 Jan 2005 01:21:41 -0000 1.27.2.4 +++ openacs-4/packages/acs-core-docs/www/apm-design.html 1 Mar 2005 00:15:52 -0000 1.27.2.5 @@ -1,7 +1,7 @@ Package Manager Design

Prev	Chapter�17.�Kernel Documentation	Next

Package Manager Design

By Bryan Quinn

OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff. -

Essentials

OpenACS Administrator directory
Package Manager Requirements
Packages
ER diagram
Tcl API
- +
Essentials
- OpenACS Administrator directory
- Package Manager Requirements
- Packages
- ER diagram
- Tcl API
  apm-procs.tcl
  apm-install-procs.tcl (Supports installation of packages)
  20-apm-load-procs.tcl (Bootstraps APM for server startup)
  @@ -87,7 +87,7 @@ packages for other OpenACS users to download and install.
  For a simple illustration of the difference between ACS without APM (pre-3.3) and ACS with APM (3.3 and beyond), consider a hypothetical ACS installation that uses only two of the thirty-odd modules available circa ACS -3.2 (say, bboard and e-commerce):
  APM itself is part of a package, the OpenACS Kernel, an OpenACS +3.2 (say, bboard and e-commerce):
  APM itself is part of a package, the OpenACS Kernel, an OpenACS service that is the only mandatory component of an OpenACS installation.
  Competitive Analysis
  The OpenACS is a platform for web-based application software, and any software platform has the potential to develop problems like those described above. Fortunately, there are many precedents for systematic solutions,