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 -r1.40.2.5 -r1.40.2.6 --- openacs-4/packages/acs-core-docs/www/apm-design.html 6 Jan 2017 09:18:41 -0000 1.40.2.5 +++ openacs-4/packages/acs-core-docs/www/apm-design.html 15 Jun 2017 13:56:41 -0000 1.40.2.6 @@ -92,9 +92,9 @@ service that is the only mandatory component of an OpenACS installation.
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, -including:
Debian GNU/Linux and the Debian +including:
Borrowing from all of the above, OpenACS 3.3 introduces its own package +collection
Borrowing from all of the above, OpenACS 3.3 introduces its own package management system, the OpenACS Package Manager (APM), which consists of:
a standard format for APM packages (also called "OpenACS packages"), including:
version numbering, independent of any other package and the OpenACS as a whole
specification of the package interface
specification of dependencies on other packages (if any)
attribution (who wrote it) and ownership (who maintains it)
web-based tools for package management:
obtaining packages from a remote distribution point
installing packages, if and only if:
all prerequisite packages are installed
no conflicts will be created by the installation
configuring packages (obsoleting the monolithic OpenACS configuration