Index: openacs-4/packages/acs-core-docs/www/apm-requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/apm-requirements.html,v diff -u -r1.26 -r1.27 --- openacs-4/packages/acs-core-docs/www/apm-requirements.html 16 Feb 2005 00:21:02 -0000 1.26 +++ openacs-4/packages/acs-core-docs/www/apm-requirements.html 4 Jun 2006 00:45:24 -0000 1.27 @@ -1,4 +1,5 @@ -Package Manager Requirements
Alex logo
Prev Chapter�17.�Kernel Documentation Next

Package Manager Requirements

By Bryan Quinn and Todd Nightingale

+ +Package Manager Requirements
Alex logo
Prev Chapter�17.�Kernel Documentation Next

Package Manager Requirements

By Bryan Quinn and Todd Nightingale

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

Introduction

The following is a requirements document for the OpenACS Package Manager @@ -97,12 +98,12 @@ exhibits different behavior.

Related Links

Requirements: Data Model

  • 4.500.0 Package Identification (All of these items are entered by the developer using the developer UI.)

    4.500.1 A human readable package key that is guaranteed to be unique to the local OpenACS site must be maintained by the APM. For -example, "apm."

    4.500.5 A package id (primary key) that is guaranteed to +example, "apm."

    4.500.5 A package id (primary key) that is guaranteed to be unique to the local site must be maintained by the APM. For example, -"25."

    4.500.10 A package URL that is guaranteed to be unique +"25."

    4.500.10 A package URL that is guaranteed to be unique across all sites must be maintained by the APM. The package URL should point to a server that allows download of the latest version of the package. For -example, "http://openacs.org/software." +example, "http://openacs.org/software."

  • 4.505.0 Version Identification (All of these items are entered by the developer using the developer UI.)

    4.505.1 A version id (primary key) that is guaranteed to be unique to the local site must be maintained by the APM.

    4.505.5 A version URL that is guaranteed to be unique @@ -182,7 +183,7 @@ XML specification to disk.

    70.5 The developer should be able to request the current XML specification for all installed, locally generated packages.

  • 130.0 Distribution file generation

    130.1 The developer should be able to generate a .APM distribution file for the package with just one click.

    130.5 Generating a distribution file implies doing an -"up-to-date" check on all of the files. If any of the files have +"up-to-date" check on all of the files. If any of the files have changed since package installation, then a new version of the package is created. @@ -266,7 +267,7 @@ This interface is part of the sub-site /admin interface.

    • 4.300 Creating a package instance.

      4.300.1 From the sub-site /admin interface, there should be an option to view all packages available in the system as well as an -option to add a package to the subsite.

      4.300.5 From the "add" option, the sub-admin +option to add a package to the subsite.

      4.300.5 From the "add" option, the sub-admin can select from a list of packages registered as available in the sub-site type to which the sub-site belongs.

      4.300.19 Once a package instance is added, it is available on the list of the subsite's available packages.

    • 4.305 Configuring a package instance.

      4.305.1 An automatic web interface that lists all