- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] wrong file on the download

by Cyril Ferlicot D.

Le 08/07/2017 Ã 20:21, Stephane Ducasse a Ã©crit : > http://pharo.org/web/download > > Pharo 7.0 image & changes > > latest.... donwloads a Pharo 60 image > This is maybe like that because the Pharo 7 images are not uploaded at files.pharo.org for now. So the latest image is the latest Pharo 6 one. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

July 9, 2017

Re: [Pharo-dev] latest 70 and vm

by Pavel Krivanek

the VM for Pharo 7 is available by zero-conf scripts ( http://get.pharo.org/vm70) or from files.pharo.org ( http://files.pharo.org/get-files/70/) We are currently not uploading Pharo 7 images to files.pharo.org. They can can be found here (32-bits): https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/ -- Pavel 2017-07-08 21:25 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Hi > > I realized that I forgot where I could find the latest 70 and vm. > So I could not update the web site > > Stef > >

July 8, 2017

latest 70 and vm

by Stephane Ducasse

Hi I realized that I forgot where I could find the latest 70 and vm. So I could not update the web site Stef

July 8, 2017

Re: [Pharo-dev] Beacon moved to github

by Norbert Hartl

You are right and I like this the most. Will change any repo I see ð Norbert > Am 08.07.2017 um 14:54 schrieb Gabriel Cotelli <g.cotelli(a)gmail.com>: > > We're using source, because you know in Smalltalk we don't like to invent abbreviations ;) > >> On Jul 8, 2017 07:18, "Esteban Lorenzano" <estebanlm(a)gmail.com> wrote: >> >> > On 8 Jul 2017, at 09:29, Tim Mackinnon <tim(a)testit.works> wrote: >> > >> > Hi Peter - I just hit this yesterday with your kind help deciphering SmalltalkCI, and I have to confess that "src" was my inclination over repository for the reason you mention in that it is a repository already. >> > >> > I noticed other STCi projects have used "packages" . >> > >> > I would vote for "src" so other newcomers more easily understand what it is compared to where they came from. >> >> yes, I agreeâ¦ even if at first is me the one who used mc, I think âsrcâis better convention, now (thatâs why pharo is using it :P) >> >> Esteban >> >> > >> > I also think it would be helpful for iceberg to default to using that so we get some consistency? >> > >> > Tim >> > >> > Sent from my iPhone >> > >> >> On 7 Jul 2017, at 17:03, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >> >> >> >>> On Fri, Jul 07, 2017 at 04:53:20PM +0200, Denis Kudriashov wrote: >> >>> Hi. >> >>> >> >>> I though it was already done :) >> >>> One notice. Should we all follow standard convention on repo structure? >> >>> Because source directory in beacon is called "repository" instead "src" >> >>> like in other repos. >> >> >> >> There is no standard convention for Pharo repos on github. >> >> >> >> In pharo-project I see >> >> >> >> * repository 3x >> >> * mc 3x >> >> * src 1x (not smalltalk code) >> >> >> >> And the rest of the github uses a variety of options >> >> >> >> * nothing >> >> - imho disorganized and very messy if you have several packages >> >> * repository >> >> - I've been using it and recommending it for ~2 years; also used by filetree and metacello repos ;) >> >> - Argument could be made that git is already a repository so it could be confusing >> >> * mc >> >> - because MontiCello/MetaCello I guess? I don't know how much this makes sense in the light of Iceberg >> >> * src >> >> - quite common in other programming languages >> >> * packages >> >> - well, the folder does contain just packages >> >> >> >> Someone could mine github to find precise numbers... but current usage shouldn't be a deciding factor. >> >> >> >> Peter >> >> >> >>> >> >>> 2017-07-07 16:45 GMT+02:00 Norbert Hartl <norbert(a)hartl.name>: >> >>> >> >>>> I used the git migration tool of Peter Uhnak to migrate Beacon from >> >>>> smalltalkhub to github. It is available now here >> >>>> >> >>>> https://github.com/pharo-project/pharo-beacon >> >>>> >> >>>> I just need to know how I can switch a smalltalkhub project to read-only. >> >>>> >> >>>> FYI, >> >>>> >> >>>> Norbert >> >>>> >> >>>> >> >> >> > >> > >> >>

July 8, 2017

wrong file on the download

by Stephane Ducasse

http://pharo.org/web/download Pharo 7.0 image & changes latest.... donwloads a Pharo 60 image

July 8, 2017

Re: [Pharo-dev] Pharo contribute page still points to Pharo50Inbox

by Stephane Ducasse

I update it to at least make sure that people know that we are in flux :) On Sat, Jul 8, 2017 at 8:04 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Thanks hernan. > We should update it to refer to github and I do not really know how to > update it. > > On Sat, Jul 8, 2017 at 6:45 PM, HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com> wrote: >> http://pharo.org/contribute-propose-fix >> >> - Also the text to the mailing list is not linked. >> - "Select the Pharo60 repository" & "Publish the slice to Pharo50Inbox" >> >> Cheers, >> >> HernÃ¡n >>

July 8, 2017

how to issue a PR that changes package structure?

by Stephane Ducasse

Hi guys I would like to split or/and create packages. Should I update the Pharo baseline. Stef

July 8, 2017

Re: [Pharo-dev] Pharo contribute page still points to Pharo50Inbox

by Stephane Ducasse

Thanks hernan. We should update it to refer to github and I do not really know how to update it. On Sat, Jul 8, 2017 at 6:45 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > http://pharo.org/contribute-propose-fix > > - Also the text to the mailing list is not linked. > - "Select the Pharo60 repository" & "Publish the slice to Pharo50Inbox" > > Cheers, > > HernÃ¡n >

July 8, 2017

Re: [Pharo-dev] Beacon moved to github

by Pierce Ng

On Fri, Jul 07, 2017 at 04:53:20PM +0200, Denis Kudriashov wrote: > One notice. Should we all follow standard convention on repo structure? > Because source directory in beacon is called "repository" instead "src" > like in other repos. In my PasswordCrypt package, I have src-c for the C sources and Makefile, and src-st for the Smalltalk code. Pierce

July 8, 2017

Pharo contribute page still points to Pharo50Inbox

by HernÃ¡n Morales Durand

http://pharo.org/contribute-propose-fix - Also the text to the mailing list is not linked. *- "**Select the Pharo60 repository" & *"Publish the slice to Pharo50Inbox" Cheers, HernÃ¡n

July 8, 2017