While SVR4 packaging does support installation of packages from networked locations over http, the support isn't great. The native support was almost never used in practice and its implementation is pretty poor (so much so that I would much rather just rip it out to simplify the code).
Allowing package installation from network repositories is expected of any modern system. However, the packaging system itself doesn't need to do so natively. There are any number of utilities and toolkits to do the network retrieval part - curl, wget, and essentially every modern scripting language will do the job.
Which leaves only the question as to what format to use in putting the data on your networked repository. The requirements here are:
- A package is packed up into a single file, to allow easy and efficient transfer using any medium
- The package should be compressed
- The contents of the package should be easily accessible on any platform without special tools
- A file should be able to contain multiple packages
The alternative solution I'm using is to simply zip up the filesystem format into a zip file. Hence, Zip Archive Packaging or zap for short.
This has the following advantages:
- Single file, can contain multiple packages
- Natively compressed
- Widespread support to unpack the archives
- Efficient random access
- Efficient extraction of list of contents
- Widely used in other contexts (eg. jar, war files)
- Some level of data integrity checking
- No need for any additional tools
- Supports extensibility for additional functionality later
So installing a package from a network repo in Tribblix is down to a very simple shell script that runs curl + unzip + pkgadd.