July 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] How to specify metacello package dependencies in a git world?

by Tim Mackinnon

Thanks Thierry - I hadnât noticed the subtle difference in URLâs - that got me further, but I think that actually the GitHub version of NeoJSON might not be totally up to date (it complains about missing version 13 on my platform - OS X. Iâve asked Sven - but I guess I should mirror what he does and load via an Mcz spec). I then think I have another problem in that my vm is the 7 version which is supposed to work with a 6 image - but I âm seeing strange working directory oddities, and I think this might be causing my other problems. Thanks, for unblocking me. Tim > On 9 Jul 2017, at 12:00, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Hi Tim, > > Le 09/07/2017 Ã 10:31, Tim Mackinnon a Ã©crit : >> Hi - I am trying to specify a simple package dependency(NeoJSON) for a hello world type simple project and Iâm hitting problems. >> Iâve been reading the DeepIntoPharo chapter and have looked at the blog post by Uko (http://blog.yuriy.tymch.uk/2015/07/pharo-and-github-versioning-revision-2.h…) >> But Iâm hitting some simple issues and Iâm hoping someone can put me straight. >> My first attempt was the following (my Package is âLambdaâ and has been versioned and put into GitHub using iceberg defaults). >> baseline: spec >> <baseline> >> spec for: #common do: [ >> spec >> package: 'Lambda' with: [ spec requires: 'NeoJSON' ]. >> spec >> project: 'NeoJSON' >> with: [ >> spec >> className: 'ConfigurationOfNeoJSON'; >> version: #stable; >> repository: >> 'https://github.com/svenvc/NeoJSON/tree/master/repository' ] >> ]. > > This url won't work: you can access a github repository either with a github: url, or a gitfiletree: url (or an iceberg url?) > > github://svenvc/NeoJSON:master/repository > > or: > > gitfiletree://github.com/svenvc/NeoJSON:master/repository > > (You may want to use a tag instead of master). > >> My first question is, what should the repository URL be? No-one seems to talk about this in the git world where the gitfile tree info can be in different places per project (some put it in the root of the repo, other src, others repository or packages etc.). Am I right in thinking this url should be where the .package file is located? > > Yes. There are repositories where you have a directory with the main packages, and other directories with secondary packages. For example, FileTree has a main repository/ directory with the packages, and many secondary repositories with test packages. > > So you need to indicate where the .package are. > >> When I try the above example by trying: >> (BaselineOfLambda project version: 'baseline') load. >> I get a talkback - Could not resolve: ConfigurationOfNeoJSON [ConfigurationOfNeoJSON] in /Users/macta/Dev/Smalltalk/Pharo/Pharo-6-60495-c/pharo-local/package-cache https://github.com/svenvc/NeoJSON/tree/master/repository >> (Strangely, that file path is wrong as its pointing to some other directory on my filesystem - and Iâve posted a question about this on the thread about the working directory implementation, as it looks like MCCacheRepository uniqueInstance is getting the wrong default directory). > > I don't know, but maybe that could be linked. Would you have preferences pointing to the wrong place ? > >> Anyway - as the above didnât work, I tried to find an example of someone else using Neo and of course Sven had and example but his looks like this: >> baseline: spec >> <baseline> >> spec for: #common do: [ >> spec configuration: 'NeoJSON' with: [ >> spec >> versionString: #stable; >> repository: 'http://mc.stfx.eu/Neo' ]. >> spec >> package: 'Lambda' with: [ spec requires: 'NeoJSON' ]. >> ]. >> I danât seen anyone mention spec configuration before (is this a better way?) - although looking at this directory, it seems this is where normal Mcz files are, so is it because of that you use this other method? >> Anyway , when I try the above - I get a similar error to the above, but now it fails loading my Lambda package (presumably because if the filesystem error?). >> Am I on the right track with the above? > > I think you are... > >> Tim > > Regards, > > Thierry >

July 9, 2017

Re: [Pharo-users] Should I be running 32bit or 64bit pharo 6?

by Esteban Lorenzano

> On 9 Jul 2017, at 12:29, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Tim, > > On 8 Jul. 2017 12:14, "Tim Mackinnon" <tim(a)testit.works> wrote: > It would be great if the snap instructions were on the download page as I can never remember them when I point fellow devs to Pharo (who often are using Linux) > > Tim > > Yep, the issue is actually proposed text for the download page. Hopefully whoever maintains that page (Esteban?) will have a chance to look at it once Pharo 7 has settled down a bit. yes, that would be me :) nevertheless, this week Iâm off because Iâm moving and is a lot more chaotic then one could believe. Even more than morphic insights ;) So well, next week I will be fixing a lot of small thingsâ¦ and preparing my presentations for ESUG :S cheers! Esteban > > Cheers, > Alistair > > > > > Sent from my iPhone > > > > Sent from my iPhone > On 7 Jul 2017, at 14:49, Alistair Grant <akgrant0710(a)gmail.com <mailto:akgrant0710@gmail.com>> wrote: > >> If you're on Ubuntu, the snap install includes the 32bit dependencies. >> >> Instructions are in https://pharo.fogbugz.com/f/cases/20147 <https://pharo.fogbugz.com/f/cases/20147> >> >> (From my phone) >> Cheers, >> Alistair >> >> >> On 7 Jul. 2017 14:06, "sergio ruiz" <sergio.rrd(a)gmail.com <mailto:sergio.rrd@gmail.com>> wrote: >> I am running the remote (live server - linux) and my development machine(macOS) 64bit.. >> >> On July 7, 2017 at 4:51:05 AM, Denis Kudriashov (dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>) wrote: >> >>> It depends on you. 64bits makes linux installation easy - no need to thing about 32bits dependency. >>> >> >> ---- >> >> peace, >> sergio >> photographer, journalist, visionary >> >> Public Key: http://bit.ly/29z9fG0 <http://bit.ly/29z9fG0> >> #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV >> http://www.Village-Buzz.com <http://www.village-buzz.com/> >> http://www.ThoseOptimizeGuys.com <http://www.thoseoptimizeguys.com/> >> http://www.coffee-black.com <http://www.coffee-black.com/> >> http://www.painlessfrugality.com <http://www.painlessfrugality.com/> >> http://www.twitter.com/sergio_101 <http://www.twitter.com/sergio_101> >> http://www.facebook.com/sergio101 <http://www.facebook.com/sergio101> >

July 9, 2017

Re: [Pharo-users] How to specify metacello package dependencies in a git world?

by Thierry Goubier

Hi Tim, Le 09/07/2017 Ã 10:31, Tim Mackinnon a Ã©crit : > Hi - I am trying to specify a simple package dependency(NeoJSON) for a > hello world type simple project and Iâm hitting problems. > > Iâve been reading the DeepIntoPharo chapter and have looked at the blog > post by Uko > (http://blog.yuriy.tymch.uk/2015/07/pharo-and-github-versioning-revision-2.h…) > > But Iâm hitting some simple issues and Iâm hoping someone can put me > straight. > > My first attempt was the following (my Package is âLambdaâ and has been > versioned and put into GitHub using iceberg defaults). > > baseline: spec > <baseline> > > spec for: #common do: [ > spec > package: 'Lambda' with: [ spec requires: 'NeoJSON' ]. > spec > project: 'NeoJSON' > with: [ > spec > className: 'ConfigurationOfNeoJSON'; > version: #stable; > repository: > > 'https://github.com/svenvc/NeoJSON/tree/master/repository' ] > ]. This url won't work: you can access a github repository either with a github: url, or a gitfiletree: url (or an iceberg url?) github://svenvc/NeoJSON:master/repository or: gitfiletree://github.com/svenvc/NeoJSON:master/repository (You may want to use a tag instead of master). > My first question is, what should the repository URL be? No-one seems to > talk about this in the git world where the gitfile tree info can be in > different places per project (some put it in the root of the repo, other > src, others repository or packages etc.). Am I right in thinking this > url should be where the .package file is located? Yes. There are repositories where you have a directory with the main packages, and other directories with secondary packages. For example, FileTree has a main repository/ directory with the packages, and many secondary repositories with test packages. So you need to indicate where the .package are. > When I try the above example by trying: > > (BaselineOfLambda project version: 'baseline') load. > > I get a talkback - Could not resolve: ConfigurationOfNeoJSON > [ConfigurationOfNeoJSON] in > /Users/macta/Dev/Smalltalk/Pharo/Pharo-6-60495-c/pharo-local/package-cache > https://github.com/svenvc/NeoJSON/tree/master/repository > > (Strangely, that file path is wrong as its pointing to some other > directory on my filesystem - and Iâve posted a question about this on > the thread about the working directory implementation, as it looks like > MCCacheRepository uniqueInstance is getting the wrong default directory). I don't know, but maybe that could be linked. Would you have preferences pointing to the wrong place ? > Anyway - as the above didnât work, I tried to find an example of someone > else using Neo and of course Sven had and example but his looks like this: > > baseline: spec > <baseline> > > spec for: #common do: [ > spec configuration: 'NeoJSON' with: [ > spec > versionString: #stable; > repository: 'http://mc.stfx.eu/Neo' ]. > spec > package: 'Lambda' with: [ spec requires: 'NeoJSON' ]. > ]. > > I danât seen anyone mention spec configuration before (is this a better > way?) - although looking at this directory, it seems this is where > normal Mcz files are, so is it because of that you use this other method? > > Anyway , when I try the above - I get a similar error to the above, but > now it fails loading my Lambda package (presumably because if the > filesystem error?). > > Am I on the right track with the above? I think you are... > Tim > Regards, Thierry

July 9, 2017

Re: [Pharo-users] Should I be running 32bit or 64bit pharo 6?

by Alistair Grant

Hi Tim, On 8 Jul. 2017 12:14, "Tim Mackinnon" <tim(a)testit.works> wrote: It would be great if the snap instructions were on the download page as I can never remember them when I point fellow devs to Pharo (who often are using Linux) Tim Yep, the issue is actually proposed text for the download page. Hopefully whoever maintains that page (Esteban?) will have a chance to look at it once Pharo 7 has settled down a bit. Cheers, Alistair Sent from my iPhone Sent from my iPhone On 7 Jul 2017, at 14:49, Alistair Grant <akgrant0710(a)gmail.com> wrote: If you're on Ubuntu, the snap install includes the 32bit dependencies. Instructions are in https://pharo.fogbugz.com/f/cases/20147 (From my phone) Cheers, Alistair On 7 Jul. 2017 14:06, "sergio ruiz" <sergio.rrd(a)gmail.com> wrote: I am running the remote (live server - linux) and my development machine(macOS) 64bit.. On July 7, 2017 at 4:51:05 AM, Denis Kudriashov (dionisiydk(a)gmail.com) wrote: It depends on you. 64bits makes linux installation easy - no need to thing about 32bits dependency. ---- peace, sergio photographer, journalist, visionary Public Key: http://bit.ly/29z9fG0 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com <http://www.village-buzz.com/> http://www.ThoseOptimizeGuys.com <http://www.thoseoptimizeguys.com/> http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

July 9, 2017

How to specify metacello package dependencies in a git world?

by Tim Mackinnon

Hi - I am trying to specify a simple package dependency(NeoJSON) for a hello world type simple project and Iâm hitting problems. Iâve been reading the DeepIntoPharo chapter and have looked at the blog post by Uko (http://blog.yuriy.tymch.uk/2015/07/pharo-and-github-versioning-revision-2.h… <http://blog.yuriy.tymch.uk/2015/07/pharo-and-github-versioning-revision-2.h…>) But Iâm hitting some simple issues and Iâm hoping someone can put me straight. My first attempt was the following (my Package is âLambdaâ and has been versioned and put into GitHub using iceberg defaults). baseline: spec <baseline> spec for: #common do: [ spec package: 'Lambda' with: [ spec requires: 'NeoJSON' ]. spec project: 'NeoJSON' with: [ spec className: 'ConfigurationOfNeoJSON'; version: #stable; repository: 'https://github.com/svenvc/NeoJSON/tree/master/repository' ] ]. My first question is, what should the repository URL be? No-one seems to talk about this in the git world where the gitfile tree info can be in different places per project (some put it in the root of the repo, other src, others repository or packages etc.). Am I right in thinking this url should be where the .package file is located? When I try the above example by trying: (BaselineOfLambda project version: 'baseline') load. I get a talkback - Could not resolve: ConfigurationOfNeoJSON [ConfigurationOfNeoJSON] in /Users/macta/Dev/Smalltalk/Pharo/Pharo-6-60495-c/pharo-local/package-cache https://github.com/svenvc/NeoJSON/tree/master/repository <https://github.com/svenvc/NeoJSON/tree/master/repository> (Strangely, that file path is wrong as its pointing to some other directory on my filesystem - and Iâve posted a question about this on the thread about the working directory implementation, as it looks like MCCacheRepository uniqueInstance is getting the wrong default directory). Anyway - as the above didnât work, I tried to find an example of someone else using Neo and of course Sven had and example but his looks like this: baseline: spec <baseline> spec for: #common do: [ spec configuration: 'NeoJSON' with: [ spec versionString: #stable; repository: 'http://mc.stfx.eu/Neo' ]. spec package: 'Lambda' with: [ spec requires: 'NeoJSON' ]. ]. I danât seen anyone mention spec configuration before (is this a better way?) - although looking at this directory, it seems this is where normal Mcz files are, so is it because of that you use this other method? Anyway , when I try the above - I get a similar error to the above, but now it fails loading my Lambda package (presumably because if the filesystem error?). Am I on the right track with the above? Tim

July 9, 2017

Re: [Pharo-users] Submitting bug fix or enhancement: still "Pharo50Inbox"?

by Stephane Ducasse

I updated the web site. On Sat, Jul 8, 2017 at 5:50 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > You should use Pharo60Inbox > > -- Pavel > > 2017-07-08 17:45 GMT+02:00 Matteo via Pharo-users > <pharo-users(a)lists.pharo.org>: >> >> >> >> ---------- PÅeposlanÃ¡ zprÃ¡va ---------- >> From: Matteo <matteob8(a)yahoo.it> >> To: "Pharo is welcome (ML)" <pharo-users(a)lists.pharo.org> >> Cc: >> Bcc: >> Date: Sat, 8 Jul 2017 17:45:15 +0200 >> Subject: Submitting bug fix or enhancement: still "Pharo50Inbox"? >> Dears, >> I would like to submit some snippet of code, as "enhancement", to >> the >> Pharo code. >> >> I'm using Pharo 6.0 image, so I thought that I should send my code >> "Pharo60Inbox", but in http://pharo.org/contribute-propose-fix is stated >> that should I send my code to the "Pharo50Inbox". >> >> Is that correct? or Should I send my code to "Pharo60Inbox"? >> >> Thanks, >> Matteo >> >> >> >

July 8, 2017

Re: [Pharo-users] 2 questions around gitlab, gitfiletree, BaselineOf

by Pierce Ng

On Fri, Jul 07, 2017 at 06:48:50AM -0700, Sabine Manaa wrote: > 1) For loading my own code, I currently have a bad solution > I would like to load it within my baseline like this below but I dont know > what to write in the fileTreeRepository method... > > baseline: spec > <baseline> > spec > for: #common > do: [ spec blessing: #baseline. > spec repository: ##self fileTreeRepository##. ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Here I use 'http://127.0.0.1:20080/', where the http server serves my filetree repo directory. The easiest way (for me on Linux/Mac) to get the http server running is 'python3 -m http.server 20080'. This method works for a directory full of .mcz files too. Pierce

July 8, 2017

Re: [Pharo-users] Submitting bug fix or enhancement: still "Pharo50Inbox"?

by Pavel Krivanek

You should use Pharo60Inbox -- Pavel 2017-07-08 17:45 GMT+02:00 Matteo via Pharo-users < pharo-users(a)lists.pharo.org>: > > > ---------- PÅeposlanÃ¡ zprÃ¡va ---------- > From: Matteo <matteob8(a)yahoo.it> > To: "Pharo is welcome (ML)" <pharo-users(a)lists.pharo.org> > Cc: > Bcc: > Date: Sat, 8 Jul 2017 17:45:15 +0200 > Subject: Submitting bug fix or enhancement: still "Pharo50Inbox"? > Dears, > I would like to submit some snippet of code, as "enhancement", to > the > Pharo code. > > I'm using Pharo 6.0 image, so I thought that I should send my code > "Pharo60Inbox", but in http://pharo.org/contribute-propose-fix is stated > that should I send my code to the "Pharo50Inbox". > > Is that correct? or Should I send my code to "Pharo60Inbox"? > > Thanks, > Matteo > > > >

July 8, 2017

Submitting bug fix or enhancement: still "Pharo50Inbox"?

by Matteo

Dears, I would like to submit some snippet of code, as "enhancement", to the Pharo code. I'm using Pharo 6.0 image, so I thought that I should send my code "Pharo60Inbox", but in http://pharo.org/contribute-propose-fix is stated that should I send my code to the "Pharo50Inbox". Is that correct? or Should I send my code to "Pharo60Inbox"? Thanks, Matteo

July 8, 2017

Re: [Pharo-users] PreDebugWindow: Report to whom?

by Stephane Ducasse

Luke use the force. It is Pharo so the code is there to browse :) On Sat, Jul 8, 2017 at 3:28 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > Hi, > > I understand that it is an obsolete (not maintained) function. The button has been removed in Pharo 7. > > Juraj > >> El 08-07-2017, a las 10:37, horrido <horrido.hobbies(a)gmail.com> escribiÃ³: >> >> In the PreDebugWindow, there is an option to Report an exception. But to whom >> does it report? I can't find any documentation for this. >> >> I presume most developers would never need to Report anything. >> >> >> >> -- >> View this message in context: http://forum.world.st/PreDebugWindow-Report-to-whom-tp4953974.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> > >

July 8, 2017