[Seaside-dev] Current Development Environment Setup

[Johan Brichau]

Philippe,

For Seaside, I’m inclined to say we can go ahead dropping support for metadataless platforms on a new release. 
For Grease, it has happened already :0 (but I was keeping an idea on fixing that if required).

Basically, if anyone wants to use latest version of Seaside/Grease on older platforms, it’s the supporting packages like Filetree others that require updating.
Dale made a good point here that it should be feasible: https://github.com/hpi-swa/smalltalkCI/issues/334#issuecomment-342575918 <https://github.com/hpi-swa/smalltalkCI/issues/334#issuecomment-342575918>

However, it seems that filetree also poses issues on Windows (file names too long) and we should rather move to Tonel format. 
Tonel also works a lot quicker checking out the repo and switching branches because of it requires far fewer files.

But I have not tried to use Tonel on Gemstone, for starters.
So, hoping to know a bit more about this at ESUG.

cheers,
Johan


> On 5 Sep 2018, at 14:09, Tobias Pape <Das.Linux at gmx.de> wrote:
> 
> Hi Philippe
>> On 05.09.2018, at 13:41, Philippe Marschall <philippe.marschall at gmail.com> wrote:
>> 
>> On Tue, Sep 4, 2018 at 12:59 PM Johan Brichau <johan at inceptive.be> wrote:
>>> 
>>> 
>>> 
>>> 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
>>> Also mind that some changes to master have not been added to develop yet: 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.
>> 
>> Thanks for the info, that helps. Do you know which platforms that would be?
> 
> For Squeak deployment metadataless works.
> For Squeak development, metadataless won't (currently) work in any version.
> 
> Best regards
> 	-Tobias
> 
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20180906/dcb914dd/attachment.html>