July 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] ConfigurationOfPharoVM

by Sean P. DeNigris

Mariano Martinez Peck wrote > > Usually, a version imports a baseline. However... you make Y > import X and you just change the ones you want. > Oh, cool! I didn't know you could do that. Thanks :) That will simplify things... Mariano Martinez Peck wrote > > btw Sean, did you know that in Metacello internals baselines and versions > are (were?) the same thing? ;) > I suspected, but wasn't sure. Sean -- View this message in context: http://forum.world.st/ConfigurationOfPharoVM-tp4639007p4639030.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 7, 2012

Re: [Pharo-project] ConfigurationOfPharoVM

by Mariano Martinez Peck

btw Sean, did you know that in Metacello internals baselines and versions are (were?) the same thing? ;) On Sat, Jul 7, 2012 at 11:16 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > PharoVM configuration names are following this rule: > > pharoversion-buildversion > > so, 2.0-1 is the first build made for pharo 2.0... > > something like that. Yeah, I don't like the numbering, but I also don't > like the M.m (Major.minor) standard, because we don't know what is major > and what minor... so, right now is just 1.9 then 2.0 without actually > having a major change.. and it is confusing, because it looks like > important, but actually it does not means anything at all :) > > Esteban > > On Jul 7, 2012, at 9:03 PM, Sean P. DeNigris wrote: > > > I noticed the versions vary between x.x.x and x.x-x and that some of the > > versions import baselines and others import other versions. I've never > seen > > it done like that... what's the intention? > > > > e.g. > > "Baseline with dot imported by version with dash" > > version145: spec > > <version: '1.4-5' imports: #('1.4.1-baseline')> > > > > "version importing another version" > > version143: spec > > <version: '1.4-3' imports: #('1.4-2')> > > > > Cheers, > > Sean > > > > -- > > View this message in context: > http://forum.world.st/ConfigurationOfPharoVM-tp4639007.html > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > -- Mariano http://marianopeck.wordpress.com

July 7, 2012

Re: [Pharo-project] ConfigurationOfPharoVM

by Mariano Martinez Peck

On Sat, Jul 7, 2012 at 9:03 PM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > I noticed the versions vary between x.x.x and x.x-x and that some of the > versions import baselines and others import other versions. I've never seen > it done like that... what's the intention? > > Usually, a version imports a baseline. However, imagine that you have several packages/projects and between version X and Y only changed a few packages. Instead of having to re-put all versions of all packages in Y, you make Y import X and you just change the ones you want. > e.g. > "Baseline with dot imported by version with dash" > version145: spec > <version: '1.4-5' imports: #('1.4.1-baseline')> > > "version importing another version" > version143: spec > <version: '1.4-3' imports: #('1.4-2')> > > Cheers, > Sean > > -- > View this message in context: > http://forum.world.st/ConfigurationOfPharoVM-tp4639007.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

July 7, 2012

Re: [Pharo-project] ConfigurationOfPharoVM

by Esteban Lorenzano

PharoVM configuration names are following this rule: pharoversion-buildversion so, 2.0-1 is the first build made for pharo 2.0... something like that. Yeah, I don't like the numbering, but I also don't like the M.m (Major.minor) standard, because we don't know what is major and what minor... so, right now is just 1.9 then 2.0 without actually having a major change.. and it is confusing, because it looks like important, but actually it does not means anything at all :) Esteban On Jul 7, 2012, at 9:03 PM, Sean P. DeNigris wrote: > I noticed the versions vary between x.x.x and x.x-x and that some of the > versions import baselines and others import other versions. I've never seen > it done like that... what's the intention? > > e.g. > "Baseline with dot imported by version with dash" > version145: spec > <version: '1.4-5' imports: #('1.4.1-baseline')> > > "version importing another version" > version143: spec > <version: '1.4-3' imports: #('1.4-2')> > > Cheers, > Sean > > -- > View this message in context: http://forum.world.st/ConfigurationOfPharoVM-tp4639007.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

July 7, 2012

Re: [Pharo-project] OSProcess test failures in Pharo 1.4

by Esteban Lorenzano

mmm... probably, but PharoVM needs an update too (btw, PharoVM is just a branded version of the cogvm, not more) Esteban On Jul 7, 2012, at 9:18 PM, Sean P. DeNigris wrote: > > Igor Stasenko wrote >> >> yeah.. it is a matter of changing the package version in >> configurationofcog >> > > VMConstruction-Plugins-OSProcessPlugin.oscog-eem.35 corresponds to > OSProcessPlugin 4.4.11 > > ConfigurationOfCog has three versions blessed development: > 4.7 - loaded by the stable version of ConfigurationOfPharoVM > 4.8 - declared as the development version for #common > 4.9 > > Since ConfigurationOfPharoVM is loading 4.7 explicitly already, it seems we > should change it from development to release, so that it is clear that it > should not be changed anymore [1]. > > Also, since 4.8 is still blessed development, why don't we merge the changes > from 4.9 into 4.8 and remove 4.9? > > If you agree with these changes, is 4.8 ready to be loaded by > ConfigurationOfPharoVM stable? > > Let me know... > Sean > > [1] After many conversations with Dale, it has sunk in that once a version > is released, it should not be changed. > > -- > View this message in context: http://forum.world.st/OSProcess-test-failures-in-Pharo-1-4-tp4638907p463901… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

July 7, 2012

Re: [Pharo-project] Cairo, VM?

by Igor Stasenko

On 7 July 2012 21:44, Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> wrote: > And for the Linux VM? > All are good? > linux NBCog should work just fine. > > Thanks > > Hilaire > > On 07/07/2012 06:26, Igor Stasenko wrote: >> RIght now for macs only.. >> https://ci.lille.inria.fr/pharo/view/NativeBoost/job/NB-Cog-Mac-Cocoa/29/ >> >> (well, actually linux one is *ready* too , you just need to install >> cairo library by yourself, >> and even, AFAIK, it is there by default in many linux distros >> >> on linux we don't need to care about bundling. >> > > > -- > Dr. Geo -- http://www.drgeo.eu > > > > -- Best regards, Igor Stasenko.

July 7, 2012

[Pharo-project] Issue with certificate on ci.lille.inria.fr preventing newImage.sh to work for iOSVM build

by phil＠highoctane.be

I was recording a screencast to show how to create the iOS VM but there was an issue. I did a git clone git://gitorious.org/~estebanlm/cogvm/cog-osx.git Then, inside cog-osx/image, I did a ./newImage.sh and got PhilMac:image philippeback$ ./newImage.sh LOADING PREBUILT IMAGE https://ci.lille.inria.fr/pharo/job/Cog%20Git%20Tracker/lastSuccessfulBuild… --2012-07-07 21:41:12-- https://ci.lille.inria.fr/pharo/job/Cog%20Git%20Tracker/lastSuccessfulBuild… RÃ©solution de ci.lille.inria.fr (ci.lille.inria.fr)... 193.49.213.180 Connexion vers ci.lille.inria.fr (ci.lille.inria.fr )|193.49.213.180|:443...connectÃ©. ERREUR : le certificat de Â«ci.lille.inria.frÂ» n'est pas digne de confiance. ERREUR : le certificat Â«ci.lille.inria.frÂ» n'est pas d'un Ã©metteur connu. FETCHING FRESH IMAGE https://ci.lille.inria.fr/pharo/job/Pharo%201.4/lastSuccessfulBuild/artifac… --2012-07-07 21:41:12-- https://ci.lille.inria.fr/pharo/job/Pharo%201.4/lastSuccessfulBuild/artifac… RÃ©solution de ci.lille.inria.fr (ci.lille.inria.fr)... 193.49.213.180 Connexion vers ci.lille.inria.fr (ci.lille.inria.fr )|193.49.213.180|:443...connectÃ©. ERREUR : le certificat de Â«ci.lille.inria.frÂ» n'est pas digne de confiance. ERREUR : le certificat Â«ci.lille.inria.frÂ» n'est pas d'un Ã©metteur connu. UNZIPPING /Users/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMiOS/cog-osx/image/image.zip Archive: image.zip End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of image.zip or image.zip.zip, and cannot find image.zip.ZIP, period. PhilMac:image philippeback$ There is something wrong with the certificate over there. Could this be fixed? TIA -- Philippe Back

July 7, 2012

Re: [Pharo-project] Cairo, VM?

by Hilaire Fernandes

And for the Linux VM? All are good? Thanks Hilaire On 07/07/2012 06:26, Igor Stasenko wrote: > RIght now for macs only.. > https://ci.lille.inria.fr/pharo/view/NativeBoost/job/NB-Cog-Mac-Cocoa/29/ > > (well, actually linux one is *ready* too , you just need to install > cairo library by yourself, > and even, AFAIK, it is there by default in many linux distros > > on linux we don't need to care about bundling. > -- Dr. Geo -- http://www.drgeo.eu

July 7, 2012

Re: [Pharo-project] OSProcess test failures in Pharo 1.4

by Sean P. DeNigris

Igor Stasenko wrote > > yeah.. it is a matter of changing the package version in > configurationofcog > VMConstruction-Plugins-OSProcessPlugin.oscog-eem.35 corresponds to OSProcessPlugin 4.4.11 ConfigurationOfCog has three versions blessed development: 4.7 - loaded by the stable version of ConfigurationOfPharoVM 4.8 - declared as the development version for #common 4.9 Since ConfigurationOfPharoVM is loading 4.7 explicitly already, it seems we should change it from development to release, so that it is clear that it should not be changed anymore [1]. Also, since 4.8 is still blessed development, why don't we merge the changes from 4.9 into 4.8 and remove 4.9? If you agree with these changes, is 4.8 ready to be loaded by ConfigurationOfPharoVM stable? Let me know... Sean [1] After many conversations with Dale, it has sunk in that once a version is released, it should not be changed. -- View this message in context: http://forum.world.st/OSProcess-test-failures-in-Pharo-1-4-tp4638907p463901… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 7, 2012

Re: [Pharo-project] Trello board for 1.4 - dead?

by Marcus Denker

On Jul 7, 2012, at 9:01 PM, phil(a)highoctane.be wrote: > I was looking at the Trello board for 1.4 and it appears dead. Is it the case? > Hmmm... it is empty because all was done when 1.4 was released... We could use it now for the TODOs that should be done? Marcus -- Marcus Denker -- http://marcusdenker.de

July 7, 2012