The following is a requirements document for the OpenACS Package Manager
(APM), version 4.0 (APM4). APM4 offers a superset of APM v3.3 functionality
@@ -155,7 +155,7 @@
adding new files, by scanning the file system for new files automatically,
and allowing the developer to confirm adding them.
20.10 The developer cannot add files to a given package
via the UI that do not exist in the file system already.
20.15 Package file structure must follow a specified
-convention. Please see the design
+convention. Please see the design
document for what we do currently.
30.0 Remove files from a package
The developer must be able to remove files from a package. This can be
done in two ways.
30.1 Access the APM UI, browse the file list, and remove
files.
30.1.1If a file is removed from the package list, but not
@@ -293,4 +293,4 @@
are set using the acs_attribute_values table. The automatic web interface for
setting package parameters should be one and the same with the interface for
setting acs object attribute values. Consequently, the implementation of
-these features should be quite straightforward.
+these features should be quite straightforward.