Ned,

Cool.  Presumably, however, packages distributed this way would bypass the
DVS fileIn mechanism... or is it smart enough to use the FilePackageLoader
if available?

On Wed, 30 Oct 2002, Ned Konz wrote:

> from preamble:
>
> "Change Set:		DVSToSAR-nk
> Date:			30 October 2002
> Author:			Ned Konz
>
> This lets you make a .sar file (complete with other files, change sets,
> preamble, and postscript) from a DVS package.
>
> I've added the following methods to PackageInfo, which may be optionally
> overridden by subclasses:
>
> prerequisiteChangeSets -- These are change sets that get loaded before
> the main change set
>
> additionalChangeSets -- These are change sets that get loaded after the
> main change set
>
> additionalFiles -- These are additional files that get extracted from
> the zip
>
> changesText -- Text of a changes log that will be shown to the user
>
> readmeText -- Text of a README file that will be shown to the user
>
> You can make a SAR file from a PackageInfo object like this:
>
> SARPackageDumper  fileOutPackage: (ConnectorsInfo someInstance) as:
> 'Connectors.sar'
> "!
>