APS:Overview
Introduction
Server
A server will provide a list divided into architectures of available packages. this would be similar to the exisiting INDEX file, but with many of the .readme headers contents. This file must be compressed to save bandwidth. A diff version showing only packages after a given date might be an option.
Package files
A package file should have its own extension so that the management tool can treat it as a package file. For instance .aps, .ami or .apm.
A package file should be a regular lh7 packed lha containing a relative hierarchy. A special dir called _APS should be used to include pre and post installation scripts and more.
A package's readme file should be used to store info about dependencies and similar.
Package management tool
Tools should exist for creating packages, installing and removing them and checking their validity. Also somethig that downloads a list of available packages.
Such a tool should make a "mirror" version of the AmigaOS system hierarchy for installing files. This hierarchy should be added to default assigns so that programs reads and writes from it before it goes further down the line.
