0299a65e45
The developer information about how you can specify the source for scripts and binaries has been having some problems, including for upgrades. The decision not to support upgrades from wheezy makes it easy to stop supporting wheezy's upgrade mechanism and begin the migration toward doing it right. Doing it right places much greater emphasis on upgrade security and integrity. The developer side of this was that the scripts ran themselves straight off a web server. That's just a problem in general, and it too will be fixed shortly. The downloading of binary components is the last thing... The right way to do this is follow the lead of @dschmenk and package this stuff properly which gains us much of that upgrade integrity/security I spoke of. That'll be a multi-step migration of its own. This will be documented as it is implemented, but here's a heads up.
847 B
A2SERVER
AppleTalk server for Apple // computers developed by Ivan Drucker
Documentation here is sparse for the moment; see Ivan's site for information about A2SERVER and how it all works. There's a lot there and it's kind of evolved organically over the years just as the scripts themselves have, so it's going to be awhile before that information can be backfilled and perhaps organized into something you might call a user manual.
Such a manual should not be considered a replacement for Ivan's organic online documentation--those contents themselves represent Apple // history, if a relatively modern piece of it. As such they should be preserved as they are.
Developer note
This section used to describe how to run these scripts directly. That's changing. Watch this space.