[Q][DOCS] How to build a SAR file?

Chris Burkert christian.burkert at s2000.tu-chemnitz.de
Thu Mar 6 10:21:17 UTC 2003


Marcus Denker wrote:
> On Thu, Mar 06, 2003 at 09:29:28AM +0100, Hannes Hirzel wrote:
> 
>>How do I build a SAR file?
> 
> 
> Yes, we need better documentation. (I'l look into this later...)
> 
> Something related:
> 
> I just discussed with Alain Fischer and Hannes how to distribute
> the ANSI Testsuite.
> 
> here's a part of the mail:
> 
> | I'm not yet totally decided what format to use for my own
> | packages: If you look at SUnit 3.1, there are changesets
> | available in the "real" cros-dialect distribution. So I'd
> | like to "just use them". (You can stuff multiple changesets
> | in a SAR).
> | This would make updating the package very simple, and it makes
> | it clear to the upstream-maintainer what we changed (because
> | that would be in it's own changeset).
> | 
> | But then I dicovered DVS: This ist *wonderful*:
> | DVS keeps track of all methods that e.g. SUnit has put
> | all over the place (Object, Collections, etc).
> |
> | You can uninstall a DVS package, or update the file on
> | disc with a single click. Or, if you download a new version
> | of an allready installed package, DVS figures out what the
> | changes are, builds a changeset on the fly and installs it.
> | 
> | So I'm pretty much sure that at this time, DVS is the way
> | to go for all bigger packages.
> | For more complex things, you can stuff DVS-Fileout into SAR-Files
> | and e.g. run postscript and install scripts.
> 
> 
> Now: I just realized that we have exactly the same problem as
> the Debian guys.
> 
> 1) DVS has features we really need (e.g. uninstall, keeping
>    track of method-additions)

Do you know the ports system of BSD? This is interesting too.

> 2) There are some packages build from cross-plattform projects
>    (SUnit, Smacc, Refatoring Browser, Ansi testsuite).
>    
>    I would like to have a scheme were we use the orinal files
>    from the distributin as much as possible.
> 
> So all in all we need some kind of solution like the .deb
> from Debian: The Squeak Packages should be build from
> the original Sources+Patches, the resulting package should
> use DVS inside a SAR. (So we would need some kind of "source
> packages" (original source+Squeak realated changes)  
> and "installation packages" (easy to install and uninstall).
> 
>     Marcus

Regards
            Chris Burkert
-- 
------------------------------------------------------------------------
Student of applied Computer Science at Chemnitz University of Technology
      http://www.chrisburkert.de/            chris at chrisburkert.de
------------------------------------------------------------------------
"I invented the term Object-Oriented, and I can tell you I did not have
  C++ in mind." - Alan Kay --> http://www.whysmalltalk.com/



More information about the Squeak-dev mailing list