April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Urgent]: Clean up Download Instructions before 4.0 Release

by phil＠highoctane.be

Le 14 avr. 2015 15:08, "Christophe Demarey" <Christophe.Demarey(a)inria.fr> a Ã©crit : > > For CentOs65, Phil has these instructions: https://github.com/philippeback/pharovm-centos65/blob/master/packages-to-in… > The only problem is the libc version an also some package names not exactly the same as the one for other distribs (ubuntu). Check for the README.md in the repo. Also this (old) http://philippeback.be/2014/02/pharovm-now-running-on-debian-wheezy/ > I also set up a job to build the vm for cent OS 6: https://ci.inria.fr/pharo/view/all/job/PharoVM-CentOs6/ > > Christophe. > > Le 14 avr. 2015 Ã 12:48, Sean P. DeNigris a Ã©crit : > > > Dale Henrichs-3 wrote > >> I've just gone through a similar process... I still have > >> not completely forgotten the magic incantations:) > > > > If anyone else has any: > > 1. magic incantations > > 2. success reports > > 2. failure reports > > for /any/ GNU/Linux Distribution/Version, please post them to this thread. I > > will review and compile everything tomorrow. > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: http://forum.world.st/Urgent-Clean-up-Download-Instructions-before-4-0-Rele… > > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > >

April 14, 2015

Re: [Pharo-dev] PetitMarkdown

by Jan KurÅ¡

Regarding completeness, it is not great. It was implement with an emphasiz on the indentation/prefix-related part (the hard one, I hope) so quoted blocks and and lists are almost complete (with arbitrary nesting). I did not need the other stuff, so there is a basic support for headers, paragraphs and code blocks. I followed the commonmark spec ( http://spec.commonmark.org/0.17/) If there is an interest to use PetitParser/CommonMark in Pharo, I can spend some time on it. I guess, I would be able to parse majority of the examples (I am not sure about all the corner cases). Cheers, Jan On 14 April 2015 at 14:24, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > On Tue, Apr 14, 2015 at 2:19 PM, Christophe Demarey < > Christophe.Demarey(a)inria.fr> wrote: > >> >> Le 14 avr. 2015 Ã 11:43, Esteban Lorenzano a Ã©crit : >> >> > how complete it is? >> > we would really like to think on: >> > >> > 1) include petitparser in Pharo >> > 2) allow the writing of class docs in MD format :) >> >> I would prefer pillar for class / packages comments >> > > I was quite surprised there are any MD defendants considering the pillar > push. But since diversity is (often) a good think maybe having something > like gt-inspector there would be cool where you can add this in whatever > format you want. (And maybe one day someone will write pillar to > morphic/whatever converter and it would be even cooler.) > > Peter > > >

April 14, 2015

Re: [Pharo-dev] [Urgent]: Clean up Download Instructions before 4.0 Release

by Christophe Demarey

For CentOs65, Phil has these instructions: https://github.com/philippeback/pharovm-centos65/blob/master/packages-to-in… The only problem is the libc version an also some package names not exactly the same as the one for other distribs (ubuntu). I also set up a job to build the vm for cent OS 6: https://ci.inria.fr/pharo/view/all/job/PharoVM-CentOs6/ Christophe. Le 14 avr. 2015 Ã 12:48, Sean P. DeNigris a Ã©crit : > Dale Henrichs-3 wrote >> I've just gone through a similar process... I still have >> not completely forgotten the magic incantations:) > > If anyone else has any: > 1. magic incantations > 2. success reports > 2. failure reports > for /any/ GNU/Linux Distribution/Version, please post them to this thread. I > will review and compile everything tomorrow. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Urgent-Clean-up-Download-Instructions-before-4-0-Rele… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

April 14, 2015

Re: [Pharo-dev] PetitMarkdown

by Peter UhnÃ¡k

On Tue, Apr 14, 2015 at 2:19 PM, Christophe Demarey < Christophe.Demarey(a)inria.fr> wrote: > > Le 14 avr. 2015 Ã 11:43, Esteban Lorenzano a Ã©crit : > > > how complete it is? > > we would really like to think on: > > > > 1) include petitparser in Pharo > > 2) allow the writing of class docs in MD format :) > > I would prefer pillar for class / packages comments > I was quite surprised there are any MD defendants considering the pillar push. But since diversity is (often) a good think maybe having something like gt-inspector there would be cool where you can add this in whatever format you want. (And maybe one day someone will write pillar to morphic/whatever converter and it would be even cooler.) Peter

April 14, 2015

Re: [Pharo-dev] PetitMarkdown

by Christophe Demarey

Le 14 avr. 2015 Ã 11:43, Esteban Lorenzano a Ã©crit : > how complete it is? > we would really like to think on: > > 1) include petitparser in Pharo > 2) allow the writing of class docs in MD format :) I would prefer pillar for class / packages comments

April 14, 2015

Re: [Pharo-dev] [Urgent]: Clean up Download Instructions before 4.0 Release

by Sean P. DeNigris

Dale Henrichs-3 wrote > I've just gone through a similar process... I still have > not completely forgotten the magic incantations:) If anyone else has any: 1. magic incantations 2. success reports 2. failure reports for /any/ GNU/Linux Distribution/Version, please post them to this thread. I will review and compile everything tomorrow. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Urgent-Clean-up-Download-Instructions-before-4-0-Rele… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 14, 2015

Re: [Pharo-dev] PetitMarkdown

by Damien Pollet

+1 PetitMarkdown (at least in the state I left it) had an incomplete and contorted grammar, translated from another implementation (the one used by pandoc, I think). I started something to handle indentation, but meh. Jan's extension of PetitParser is the way to go, and it should make the grammar way more readable. On 14 April 2015 at 11:43, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > how complete it is? > we would really like to think on: > > 1) include petitparser in Pharo > 2) allow the writing of class docs in MD format :) > > of course, we are talking about the not-so-near future, but is an idea we > are thinking aboutâ¦ :P > > and in any case, I would like to use a good MD parser for my own stuff :) > > Esteban > > On 14 Apr 2015, at 10:42, Jan KurÅ¡ <kurs(a)iam.unibe.ch> wrote: > > Hey, > > I also created an indentation sensitive extension of PetitParser, I also > included some examples including Markdown. If you load PetitParser, you get > the Markdown example as well. > > There is a short introduction to the indentation: > > http://scg.unibe.ch/research/indentParsing > > Cheers Jan > On Apr 13, 2015 5:24 PM, "H. Hirzel" <hannes.hirzel(a)gmail.com> wrote: > >> Are there any news on this? >> >> --Hannes >> >> On 12/28/14, Norbert Hartl <norbert(a)hartl.name> wrote: >> > I found markdown parsers in smalltalkhub and in the configuration >> browser. >> > >> > http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ >> > <http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/> >> > >> > and the one in the configuration browser >> > >> > PPMarkdown >> > >> > If I understand it correctly both are rooted into work Camillo did. The >> one >> > in PharoExtras looks newer to me. So I assume the best would be to copy >> the >> > ConfigurationOfPetitMarkdown from PharoExtras to MetacelloRepo and >> remove >> > the ConfigurationOfPPMarkdown. Right? Or are there any objections? >> > >> > Norbert >> >> > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

April 14, 2015

[pharo-project/pharo-core] da8d8e: 40608

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: da8d8e63d16d9294889744d9a5c672108fbf8878 https://github.com/pharo-project/pharo-core/commit/da8d8e63d16d9294889744d9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-14 (Tue, 14 Apr 2015) Changed paths: R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script607.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script608.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40607.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40608.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40608 new .sources http://files.pharo.org/image/40/40608.zip

April 14, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40608 Home: https://github.com/pharo-project/pharo-core

April 14, 2015

Re: [Pharo-dev] [Urgent]: Clean up Download Instructions before 4.0 Release

by Sean P. DeNigris

Dale Henrichs-3 wrote > The basic trick is to run `ldd` against the plugin/.so files in the vm > directory and IIRC, you get a "not found" message for the missing > libraries and I just tacked :i386 onto library name for `apt-get`... This is getting interesting? Do you think the process could be automated? Like maybe part of the ZeroConf scripts? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Urgent-Clean-up-Download-Instructions-before-4-0-Rele… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 14, 2015