Sig, I just noted that Alien-examples contains a couple of classes with no methods. Where can I find examples of callbacks in action? Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Schwab,Wilhelm K [bschwab@anest.ufl.edu] Sent: Wednesday, February 29, 2012 12:13 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3 Sig, I went back to 1.3 to get shout in browsers, and because it is theoretically more stable than 1.4. AFAIK, the key to finding libraries on Ubuntu is to use the #moduleName. Integration of the load function with ldconfig will do the rest, or should. The idea is a good one: one needs root access to change ldconfig's map, but anyone can read it. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Igor Stasenko [siguctua@gmail.com] Sent: Wednesday, February 29, 2012 10:01 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3 On 29 February 2012 14:57, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
Sig,
I appear to a 1.3 image in preliminary state. I'm sure stuff will be broken, and Cog is rearing its head by looking for external libraries in the wrong places; symlinks should clear that up, but it's ugly.
Bill, it's not about 1.3 or 1.4. it is how VM works (symlinks/lib search). In this regard, any pharo version is not anything better than other. Yes, we need to change that at some day.
I used the 1.3 seaside image as a base, and will have Seaside 2-3 problems to fix. Alien was the problem, probably breaking the compiler, as you suggested.
To correct you: it was not a suggestion. When Alien was released there was need to change compiler/parser in order to make it work. Eliot made a separate package for that. Now, after those changes were incorporated into Pharo itself, they are no longer needed. and moreover they might override existing methods with older/incompatible versions of it coming from Alien. Overrides are evil. Overrides in kernel are evil^2 :)
Bill
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Igor Stasenko [siguctua@gmail.com] Sent: Sunday, February 26, 2012 9:50 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3
On 25 February 2012 11:15, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
Sig,
This is helpful, as you have told me what is killing my images. Then you say to load then you say to load the latest config. Happy to comply, but how do I do that?
(ConfigurationOfWhatever project version: 'x.y.z') load
or better learn more about metacello, there's a well-written chapter of it from the guys who care https://gforge.inria.fr/scm/viewvc.php/*checkout*/PharoByExampleTwo-Eng/Meta...
Bill
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Igor Stasenko [siguctua@gmail.com] Sent: Saturday, February 25, 2012 12:39 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [Bug Tracker] Issues tagged 1.3
On 25 February 2012 06:52, Igor Stasenko <siguctua@gmail.com> wrote:
On 25 February 2012 06:35, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
Sig,
Sorry about the empty reply. Migrate is fair game, and the image was healthy enough to file out the base (attached). Please look over how I install FFI to see if there are any mistakes. You might need to stub out a basic subclass (e.g. MigrateSig or anything else you want to call it) with a few methods (#me, #homeGrownClasses, etc.) to make it happy. Content of them can be simple to start. The "private stuff" has yet to enter the picture so shouldn't matter to us.
THANKS!!!
Good. I will take a look.
Bill
Ok, things for starting:
Gofer new url:self mirror, 'MetacelloRepository'; package: 'ConfigurationOfAlien'; load. (Smalltalk globals classNamed: 'ConfigurationOfAlien') perform:#loadLatestVersion.
Never ever use #loadLatestVersion, always use concrete version numbers, if you want to have stability.
In our case, #loadLatestVersion is not quite latest, you can check it by yourself:
ConfigurationOfAlien project updateProject. ConfigurationOfAlien project latestVersion "inspect it"
0.1 [ConfigurationOfAlien] so it actually loads not the latest available version, but the most old one. Because it is the only version with #release blessing.
And i can tell you without even proceeding further, that it won't work in 1.3 neither in 1.4, because it is too old and not takes into account certain changes made in pharo.
For instance:
package: 'Alien-Prereqs'
is no longer needed, as i told here:
http://forum.world.st/Alien-Prerequisites-is-now-not-required-td3258432.html
but its even worse, this version of config will be loading Alien-Prereqs-mha.3 which having even more overrides, and will definitely put image to its knees because compiler will be broken.
So, try to load latest config first, if it would not help we will continue.
P.S. to all people involved in using Alien.. some love needed to update configs for pharo 1.3 and 1.4 to finally get rid of 'Alien-Prereqs' package loading.
-- Best regards, Igor Stasenko.
-- Best regards, Igor Stasenko.
-- Best regards, Igor Stasenko.