Fw: Getting Coral to load on Linux / Pharo 1.1

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Fw: Getting Coral to load on Linux / Pharo 1.1

nickdavis

------------------------------------------------

Nick Davis
Software Developer (Infrastructure)

----- Forwarded by Nick Davis/UK/Romax on 13/02/2012 16:05 -----


    From:

Nick Davis/UK/Romax

    To:

Mariano Martinez Peck <[hidden email]>,

    Date:

13/02/2012 16:05

    Subject:

Re: [Pharo-coral] Getting Coral to load on Linux / Pharo 1.1



Hello Mariono, Damien, Stephane,
   Thanks for the replies. I shall proceed with caution and not expect too much of Coral at this stage. It looks extremely promising though. Very nice to be able to run shell scripts that talk directly to a Pharo image. Brilliant for cron jobs that run regular scripts etc. Or for uploading new code to a production system without taking it down.
Regards,
Nick


-----------------------------------------------




Inactive hide details for Mariano Martinez Peck ---13/02/2012 13:51:10---On Mon, Feb 13, 2012 at 2:37 PM, Nick Davis <Nick.DaviMariano Martinez Peck ---13/02/2012 13:51:10---On Mon, Feb 13, 2012 at 2:37 PM, Nick Davis <[hidden email]>wrote: > Hello,


    From:

Mariano Martinez Peck <[hidden email]>

    To:

Nick Davis <[hidden email]>,

    Cc:

[hidden email]

    Date:

13/02/2012 13:51

    Subject:

Re: [Pharo-coral] Getting Coral to load on Linux / Pharo 1.1






On Mon, Feb 13, 2012 at 2:37 PM, Nick Davis <[hidden email]> wrote:
    Hello,
      If you do -
    Gofer new url: '
    http://ss3.gemstone.com/ss/coral';    package: 'ConfigurationOfCoral';    load.

      followed by
    ConfigurationOfCoral loadDevelopment


    This works fine on Pharo 1.3  (Centos6 platform) ,  but on Pharo 1.1 it fails to load.
    It blows up in ConfigurationOfCoral class>>loadDevelopment  because (self project version: #development) returns nil.



That's because symbolic versions (like #development) were added in newer versions of Metacello than the one provided out of the box in Pharo 1.1. You can update Metacello (something like ConfigurationOfMetacello load)  or to use an specific numbered version of Coral.

 
    Any advice on how to make this work?  Is Pharo 1.1 even supported?

    Thanks a lot,
    Nick Davis







--
Mariano

http://marianopeck.wordpress.com
_______________________________________________
Pharo-coral mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-coral



============================================= Romax Technology Limited Rutherford House Nottingham Science & Technology Park Nottingham, NG7 2PZ England Telephone numbers: +44 (0)115 951 88 00 (main) For other office locations see: http://www.romaxtech.com/Contact ================================= =============== E-mail: [hidden email] Website: www.romaxtech.com ================================= ================ Confidentiality Statement This transmission is for the addressee only and contains information that is confidential and privileged. Unless you are the named addressee, or authorised to receive it on behalf of the addressee you may not copy or use it, or disclose it to anyone else. If you have received this transmission in error please delete from your system and contact the sender. Thank you for your cooperation. =================================================
_______________________________________________
Pharo-coral mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-coral
Loading...