Right, and a file-in mechanism generalized to handle zips would allow you to
have a snippet of code at the beginning of a SAR that called the
install/preamble.

Anyway, it's not so important to me that I'm about to run off and write it.

- Stephen

> -----Original Message-----
> From: squeak-dev-admin at lists.squeakfoundation.org
> [mailto:squeak-dev-admin at lists.squeakfoundation.org]On Behalf Of
> goran.hultgren at bluefish.se
> Sent: Wednesday, November 20, 2002 10:36 AM
> To: squeak-dev at lists.squeakfoundation.org
> Subject: RE: SAR
>
>
> "Stephen Pair" <spair at acm.org> wrote:
> > Yes, I may not be the brightest person, but I do know they are
> zip files and
> > I know you want to put other stuff in there.
> >
> > What I'm proposing is to generalize things a bit and make it so that the
> > file in mechanism gives you enough support that you can put a
> chunk of code
> > at the beginning of a zip file and then manipulate that zip
> file in whatever
> > way you want (i.e. load the change set and package members,
> copy images and
> > other files to a certain location, etc).  That would be entirely
> > complementary to the SAR conventions.
> >
> > - Stephen
>
> Currently this is done throught the "preamble" file inside the .sar
> file.
> As Andreas said - all this works today with the only difference that you
> can't just use the normal "file in" mechanism, you need to go through
> the SAR installer class.
>
> But personally I don't think that is a problem - it might even be a good
> thing - we should strive in moving away from the old formats in favor of
> the new ones IMHO.
>
> regards, Göran
>
>
>