January 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] How to specify generic (non-github) git dependency?

by Dale Henrichs

Herby, Right now there is "no portable way" to specify arbitrary hosts in a Metacello spec ... but Esteban and I will be talking about this on Monday ... Thierry Goubier seems to have a nice scheme for gitfiletree and I think that iceberg might support additional urls and schemes... Dale On 01/28/2018 01:52 AM, Herbert VojÄÃk wrote: > Hi, > > I know I can do, for example, > > [..snip..] > Â Â Â Â package: 'Foo' with: [ spec > Â Â Â Â Â Â Â requires: #('Mocketry') ]; > > Â Â Â Â baseline: 'Mocketry' with: [ spec > Â Â Â Â Â Â Â repository: 'github://dionisiydk/Mocketry:v4.0.x' ]; > [..snip..] > > but when I want to add dependency to a repo which is not on github nor > on bitbucket, how do I specify (https or scp) git depedency in generic > way? > > Thanks, Herby >

Jan. 28, 2018

Re: [Pharo-users] New booklets organisation and new booklet

by phil＠highoctane.be

Looks nice. We should also put the books of Dr Geo in there but maybe they are GPL. But at least a link to http://www.drgeo.eu/help would be nice. Phil On Sun, Jan 28, 2018 at 10:47 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > +1 > > > On 27 Jan 2018, at 20:55, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > > > Hi > > > > We reorganised the books.pharo.org web site to make the distinction > > between technology and teaching oriented booklet. > > We will have specific covers soon and print available on lulu. > > > > In addition we got the new booklet from C. Bera that explains Call > > Stack Management. > > > > http://books.pharo.org > > > > Stef > > > > > >

Jan. 28, 2018

Re: [Pharo-users] Iceberg and resource files

by kmo

These suggestions look really good. Thanks to everyone. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 28, 2018

How to specify generic (non-github) git dependency?

by Herbert VojÄÃk

Hi, I know I can do, for example, [..snip..] package: 'Foo' with: [ spec requires: #('Mocketry') ]; baseline: 'Mocketry' with: [ spec repository: 'github://dionisiydk/Mocketry:v4.0.x' ]; [..snip..] but when I want to add dependency to a repo which is not on github nor on bitbucket, how do I specify (https or scp) git depedency in generic way? Thanks, Herby

Jan. 28, 2018

Re: [Pharo-users] New booklets organisation and new booklet

by Esteban Lorenzano

+1 > On 27 Jan 2018, at 20:55, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi > > We reorganised the books.pharo.org web site to make the distinction > between technology and teaching oriented booklet. > We will have specific covers soon and print available on lulu. > > In addition we got the new booklet from C. Bera that explains Call > Stack Management. > > http://books.pharo.org > > Stef >

Jan. 28, 2018

Re: [Pharo-users] Iceberg and resource files

by Peter UhnÃ¡k

Hi, > How do I include these in the iceberg commit/push? > How do I see changes made in these files from version to version? Apart from directly using the actual git repo outside of pharo, you can use the facade provided by IceRepository, or you can use libgit inside Pharo. E.g. to add an external file to index (which will be then committed together with new code) repo := IceRepository registry detect: [ :each | each name = 'some-repo' ]. repo addFilesToIndex: {'README.md'}. Peter On Sun, Jan 28, 2018 at 6:23 AM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > Hi Ken, > > Some days ago I published a package to manage download of resources > from Metacello configurations. > Have a look at https://github.com/hernanmd/MetacelloFileDownload > > HernÃ¡n > > > 2018-01-27 11:38 GMT-03:00 kmo <voxkmp(a)gmail.com>: > > I don't understand how iceberg handles resource files that you might also > > like to version along with the pharo code. > > > > Say I have an CSV file and a text file that my pharo application uses. > How > > do I include these in the iceberg commit/push? How do I see changes made > in > > these files from version to version? > > > > Does iceberg only handle pharo code? Generally git clients don't care > about > > the file type - and it it is any kind of text you can see the actual > > differences between each commit. > > > > Ken > > > > > > > > -- > > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > >

Jan. 28, 2018

Re: [Pharo-users] Download pillar image -> Error 403: Forbidden

by HernÃ¡n Morales Durand

Hi Stef, 2018-01-28 4:15 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Ok I see. I think that I never tried this version of Pillar on windows. > And I hate make because it is impossible for me to debug it. I will > check with Damien > because I do not get make. > > Now we removed the dependency to make in the dev branch > Could you try the following: > https://github.com/pillar-markup/pillar/blob/newpipeline/README.md > Tried both options, 1) downloading pre-compiled and 2) building from sources+setting up environment. 1) Nothing happened after "pillar archetype build", exit without error, no stdout output, no _result folder 2) I got confused with this: mv pillar ~/.pillar because now I have two directories: the .pillar in HOME and the build/ directory separated. And no "pillar" shell script so should I copy the one from 1) ? I will re-check tomorrow maybe I'm reading this the wrong way. > so that I can see if this is working. > I know that guille worked on windows and AppVeyor support but he got > distracted by the github refactoring. > We hope to come back this week to Pillar. We plan to release a version > (still with Magritte) but with a full documentation. > Cool, I will test because I have several chapters ready to publish. > Stef > > > > > > On Sat, Jan 27, 2018 at 4:47 PM, HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com> wrote: >> Hi Stef >> >> 2018-01-27 9:30 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>> Hi Hernan >>> >>> >>> >>> On Thu, Jan 25, 2018 at 10:30 PM, HernÃ¡n Morales Durand >>> <hernan.morales(a)gmail.com> wrote: >>>> I am following the Publishing Pillar Booklet guide from here >>>> https://github.com/SquareBracketAssociates/Booklet-PublishingAPillarBooklet >>> >>> pay attention it is not public because it is in flux because we were >>> working on Pillar 70. >>> >>> Now if you follow the readme of pillar-markup/pillar/ it should work >>> since I used it yesterday. >>> >>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >>>> $ chmod +x download.sh >>>> $ ./download.sh >>> >>>>./pillar archetype book >>> make book. >>> >>> >>> What you should know is that the stable version sucks at the >>> infrastructure level (relying on too many servers + silent failures in >>> bash files). >>> >>> Can you retry and let me know? >> >> Ok I tried again using MinGW in Windows 8.1 >> Image is downloaded ok but final step gives an error: >> >> $ make book >> support/makefiles/prepare.mk:1: *** Undefined setting OUTPUTDIRECTORY (Directory >> for build products). Stop. >> >> I replaced the expanded shell variables in main.mk from using := to = >> and it seems to "solve" this problem, though someone else should check >> why this happens >> >> MAIN = $(shell ./pillar introspect mainDocument) >> >> OUTPUTDIRECTORY = $(shell ./pillar introspect outputDirectory) >> LATEXTEMPLATE = $(shell ./pillar introspect latexTemplate) >> LATEXCHAPTERTEMPLATE = $(shell ./pillar introspect latexChapterTemplate) >> HTMLTEMPLATE = $(shell ./pillar introspect htmlTemplate) >> HTMLCHAPTERTEMPLATE = $(shell ./pillar introspect htmlChapterTemplate) >> CHAPTERS = $(shell ./pillar introspect chapters) >> >> $ make book >> make: *** No rule to make target `/.pdf', needed by `pdfbook'. Stop. >> >> I am using >> $ make --version >> GNU Make 3.81 >> >> >>> BTW why do you want to compile Booklet-PublishingAPillarBooklet/ >>> If you want just create your own repo and do >>> >>> wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >>> chmod +x download.sh >>> ./download.sh >>> ./pillar archetype book >>> make book. >>> >> >> Thanks, I just followed the install instructions. >> >> HernÃ¡n >> >>> >>> Stef >>> >>> >>>> $ git clone git@github.com:SquareBracketAssociates/Booklet-PublishingAPillarBooklet.git >>>> $ cd Booklet-PublishingAPillarBooklet/ >>>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >>>> $ chmod +x download.sh >>>> $ ./download.sh >>>> >>>> --2018-01-25 17:56:32-- http://get.pharo.org/vm50 >>>> Resolving get.pharo.org (get.pharo.org) 164.132.235.17 >>>> Connecting to get.pharo.org (get.pharo.org)|164.132.235.17|:80... connected. >>>> HTTP request sent, awaiting response... 200 OK >>>> Length: 5819 (5.7K) >>>> Saving to: 'STDOUT' >>>> >>>> 0K ..... 100% 371K=0.02s >>>> >>>> 2018-01-25 17:56:33 (371 KB/s) - written to stdout [5819/5819] >>>> >>>> Downloading the latest pharoVM: >>>> http://files.pharo.org/get-files/50/pharo-win-stable.zip >>>> pharo-vm/Pharo.exe >>>> Downloading PharoV50.sources: >>>> http://files.pharo.org/get-files/50/sources.zip >>>> Creating starter scripts pharo and pharo-ui >>>> --2018-01-25 17:57:21-- >>>> https://github.com/pillar-markup/pillar/releases/download/50/Pillar-deploym… >>>> Resolving github.com (github.com) 192.30.253.112, 192.30.253.113 >>>> Connecting to github.com (github.com)|192.30.253.112|:443... connected. >>>> HTTP request sent, awaiting response... 302 Found >>>> Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/41843105/f4… >>>> [following] >>>> --2018-01-25 17:57:23-- >>>> https://github-production-release-asset-2e65be.s3.amazonaws.com/41843105/f4… >>>> Resolving github-production-release-asset-2e65be.s3.amazonaws.com >>>> (github-production-release-asset-2e65be.s3.amazonaws.com) >>>> 54.231.115.35 >>>> Connecting to github-production-release-asset-2e65be.s3.amazonaws.com >>>> (github-production-release-asset-2e65be.s3.amazonaws.com)|54.231.115.35|:443... >>>> connected. >>>> HTTP request sent, awaiting response... 200 OK >>>> Length: 18482449 (18M) [application/octet-stream] >>>> Saving to: 'imageLn5zD.zip' >>>> >>>> imageLn5zD.zip 10%[=> ] 1.88M 502 B/s in 8m 7s >>>> >>>> 2018-01-25 18:15:45 (3.94 KB/s) - Read error at byte 1966661/18482449 >>>> (Bad file descriptor). Retrying. >>>> >>>> --2018-01-25 18:15:46-- (try: 2) >>>> https://github-production-release-asset-2e65be.s3.amazonaws.com/41843105/f4… >>>> Connecting to github-production-release-asset-2e65be.s3.amazonaws.com >>>> (github-production-release-asset-2e65be.s3.amazonaws.com)|54.231.115.35|:443... >>>> connected. >>>> HTTP request sent, awaiting response... 403 Forbidden >>>> 2018-01-25 18:15:47 ERROR 403: Forbidden. >>>> >>>> >>>> Also the download speed was super slow. >>>> >>>> Any ideas? >>>> >>>> Cheers, >>>> >>>> HernÃ¡n >>>> >>> >> >

Jan. 28, 2018

Re: [Pharo-users] Download pillar image -> Error 403: Forbidden

by Stephane Ducasse

Ok I see. I think that I never tried this version of Pillar on windows. And I hate make because it is impossible for me to debug it. I will check with Damien because I do not get make. Now we removed the dependency to make in the dev branch Could you try the following: https://github.com/pillar-markup/pillar/blob/newpipeline/README.md so that I can see if this is working. I know that guille worked on windows and AppVeyor support but he got distracted by the github refactoring. We hope to come back this week to Pillar. We plan to release a version (still with Magritte) but with a full documentation. Stef On Sat, Jan 27, 2018 at 4:47 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Hi Stef > > 2018-01-27 9:30 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> Hi Hernan >> >> >> >> On Thu, Jan 25, 2018 at 10:30 PM, HernÃ¡n Morales Durand >> <hernan.morales(a)gmail.com> wrote: >>> I am following the Publishing Pillar Booklet guide from here >>> https://github.com/SquareBracketAssociates/Booklet-PublishingAPillarBooklet >> >> pay attention it is not public because it is in flux because we were >> working on Pillar 70. >> >> Now if you follow the readme of pillar-markup/pillar/ it should work >> since I used it yesterday. >> >> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >>> $ chmod +x download.sh >>> $ ./download.sh >> >>>./pillar archetype book >> make book. >> >> >> What you should know is that the stable version sucks at the >> infrastructure level (relying on too many servers + silent failures in >> bash files). >> >> Can you retry and let me know? > > Ok I tried again using MinGW in Windows 8.1 > Image is downloaded ok but final step gives an error: > > $ make book > support/makefiles/prepare.mk:1: *** Undefined setting OUTPUTDIRECTORY (Directory > for build products). Stop. > > I replaced the expanded shell variables in main.mk from using := to = > and it seems to "solve" this problem, though someone else should check > why this happens > > MAIN = $(shell ./pillar introspect mainDocument) > > OUTPUTDIRECTORY = $(shell ./pillar introspect outputDirectory) > LATEXTEMPLATE = $(shell ./pillar introspect latexTemplate) > LATEXCHAPTERTEMPLATE = $(shell ./pillar introspect latexChapterTemplate) > HTMLTEMPLATE = $(shell ./pillar introspect htmlTemplate) > HTMLCHAPTERTEMPLATE = $(shell ./pillar introspect htmlChapterTemplate) > CHAPTERS = $(shell ./pillar introspect chapters) > > $ make book > make: *** No rule to make target `/.pdf', needed by `pdfbook'. Stop. > > I am using > $ make --version > GNU Make 3.81 > > >> BTW why do you want to compile Booklet-PublishingAPillarBooklet/ >> If you want just create your own repo and do >> >> wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >> chmod +x download.sh >> ./download.sh >> ./pillar archetype book >> make book. >> > > Thanks, I just followed the install instructions. > > HernÃ¡n > >> >> Stef >> >> >>> $ git clone git@github.com:SquareBracketAssociates/Booklet-PublishingAPillarBooklet.git >>> $ cd Booklet-PublishingAPillarBooklet/ >>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >>> $ chmod +x download.sh >>> $ ./download.sh >>> >>> --2018-01-25 17:56:32-- http://get.pharo.org/vm50 >>> Resolving get.pharo.org (get.pharo.org) 164.132.235.17 >>> Connecting to get.pharo.org (get.pharo.org)|164.132.235.17|:80... connected. >>> HTTP request sent, awaiting response... 200 OK >>> Length: 5819 (5.7K) >>> Saving to: 'STDOUT' >>> >>> 0K ..... 100% 371K=0.02s >>> >>> 2018-01-25 17:56:33 (371 KB/s) - written to stdout [5819/5819] >>> >>> Downloading the latest pharoVM: >>> http://files.pharo.org/get-files/50/pharo-win-stable.zip >>> pharo-vm/Pharo.exe >>> Downloading PharoV50.sources: >>> http://files.pharo.org/get-files/50/sources.zip >>> Creating starter scripts pharo and pharo-ui >>> --2018-01-25 17:57:21-- >>> https://github.com/pillar-markup/pillar/releases/download/50/Pillar-deploym… >>> Resolving github.com (github.com) 192.30.253.112, 192.30.253.113 >>> Connecting to github.com (github.com)|192.30.253.112|:443... connected. >>> HTTP request sent, awaiting response... 302 Found >>> Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/41843105/f4… >>> [following] >>> --2018-01-25 17:57:23-- >>> https://github-production-release-asset-2e65be.s3.amazonaws.com/41843105/f4… >>> Resolving github-production-release-asset-2e65be.s3.amazonaws.com >>> (github-production-release-asset-2e65be.s3.amazonaws.com) >>> 54.231.115.35 >>> Connecting to github-production-release-asset-2e65be.s3.amazonaws.com >>> (github-production-release-asset-2e65be.s3.amazonaws.com)|54.231.115.35|:443... >>> connected. >>> HTTP request sent, awaiting response... 200 OK >>> Length: 18482449 (18M) [application/octet-stream] >>> Saving to: 'imageLn5zD.zip' >>> >>> imageLn5zD.zip 10%[=> ] 1.88M 502 B/s in 8m 7s >>> >>> 2018-01-25 18:15:45 (3.94 KB/s) - Read error at byte 1966661/18482449 >>> (Bad file descriptor). Retrying. >>> >>> --2018-01-25 18:15:46-- (try: 2) >>> https://github-production-release-asset-2e65be.s3.amazonaws.com/41843105/f4… >>> Connecting to github-production-release-asset-2e65be.s3.amazonaws.com >>> (github-production-release-asset-2e65be.s3.amazonaws.com)|54.231.115.35|:443... >>> connected. >>> HTTP request sent, awaiting response... 403 Forbidden >>> 2018-01-25 18:15:47 ERROR 403: Forbidden. >>> >>> >>> Also the download speed was super slow. >>> >>> Any ideas? >>> >>> Cheers, >>> >>> HernÃ¡n >>> >> >

Jan. 28, 2018

Re: [Pharo-users] Iceberg and resource files

by HernÃ¡n Morales Durand

Hi Ken, Some days ago I published a package to manage download of resources from Metacello configurations. Have a look at https://github.com/hernanmd/MetacelloFileDownload HernÃ¡n 2018-01-27 11:38 GMT-03:00 kmo <voxkmp(a)gmail.com>: > I don't understand how iceberg handles resource files that you might also > like to version along with the pharo code. > > Say I have an CSV file and a text file that my pharo application uses. How > do I include these in the iceberg commit/push? How do I see changes made in > these files from version to version? > > Does iceberg only handle pharo code? Generally git clients don't care about > the file type - and it it is any kind of text you can see the actual > differences between each commit. > > Ken > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Jan. 28, 2018

New booklets organisation and new booklet

by Stephane Ducasse

Hi We reorganised the books.pharo.org web site to make the distinction between technology and teaching oriented booklet. We will have specific covers soon and print available on lulu. In addition we got the new booklet from C. Bera that explains Call Stack Management. http://books.pharo.org Stef

Jan. 27, 2018