[Seaside-dev] Current Development Environment Setup

Johan Brichau johan at inceptive.be
Tue Sep 4 10:59:03 UTC 2018



> On 4 Sep 2018, at 11:54, Philippe Marschall <philippe.marschall at gmail.com> wrote:
> 
> Hi
> 
> I'd like to hit the ground running at ESUG and arrive with a working
> development environment for at ESUG. I'd appreciate it if somebody
> could answer me the following questions
> - What is the recommended Pharo Version on macOS X? I'm using
> PharoLauncher to download 6.1 32 bit and ignore the warnings.
> Downloading 6.1 directly results in corrupt files

I’m using 6.1 64-bit (direct downloads) and 7 (via PharoLauncher).

Pharo 7 version of Seaside is WIP: https://github.com/SeasideSt/Seaside/tree/pharo7 <https://github.com/SeasideSt/Seaside/tree/pharo7>
Also mind that some changes to master have not been added to develop yet: https://github.com/SeasideSt/Seaside/pull/989 <https://github.com/SeasideSt/Seaside/pull/989>
> - How do I checkout the code and load it into the image? My last
> information was that both Grease and Seaside as FileTree repositories,
> and that Grease is metadata-less. Is this still correct?

Correct, except that Grease is metadataless only for the Pharo7 package (since I did that with Iceberg).
Unfortunately, that makes it unloadable in Pharo3-4 as well.

> Should I
> check out using git and then add the Monticello repositories or should
> I use Metacello? Should I use Iceberg or rather not?

Using Iceberg means: metadataless and thus we drop support for a number of platforms.

TBD?

Johan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20180904/1394a30e/attachment.html>


More information about the seaside-dev mailing list