January 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Contributing to Pharo

by Sven Van Caekenberghe

> On 16 Jan 2016, at 14:44, Ben Coman <btc(a)openinworld.com> wrote: > > On Sat, Jan 16, 2016 at 7:25 PM, David Allouche <david(a)allouche.net> wrote: >> >>> On 16 Jan 2016, at 12:14, stepharo <stepharo(a)free.fr> wrote: >>> >>> Le 16/1/16 09:59, David Allouche a Ã©crit : >>>> >>>> But, really, this "list of dirty packages" should really only list dirty packages. What is the use case for selecting a non-dirty package? >>> >>> because you never know >>> Sometimes you save a package then you do a slice and you should be able to decide. >> >> That does not make sense to me. I guess it will, when I understand Monticello better. >> >> > > Its a very corner case. I've had to do it on occasion but I can't > exactly remember the circumstance. Now what might be useful is a > checkbox for displaying non-dirty packages - so we only display the > short list in the usual case. (??) +100 it is very confusing right now > cheers -ben >

Jan. 16, 2016

Re: [Pharo-dev] Git repository and branch for spur enable pharo-vm

by Mariano Martinez Peck

Hi, Today I was also needed to compile Spur VM and just by chance by this email I found out I should be using Esteban fork. So maybe at least a sentence in the original repo saying that for Spur / Pharo 5.0 you should use Esteban fork would help. At least until you merge. Cheers, On Fri, Jan 15, 2016 at 5:23 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > > On 15 Jan 2016, at 18:29, Holger Freyther <holger(a)freyther.de> wrote: > > > > Hi, > > > > what is the official pharo-vm git repository? It looks like > github.com/pharo-project/pharo-vm is not being updated right now. It > looks like esteban's fork is currently being used and the spur64 branch. Is > that correct? Can it it to be used for spur32 and spure64? Is there any > plan to merge this back into a repositpory in pharo-project/pharo-vm? > > yes to everything :) > > - right now is the one Iâm updating > - it will be merged with pharo-project (I didnât have the time to do it, > but it will be soon) > - you can do a spur32 and theoretically a stack 64bits, but since we still > do not have a 64bits image (one of my soon (â¢) next steps) it doesnât looks > meaningful right now :) > > cheers, > Esteban > > > > > kind regards > > holger > > > -- Mariano http://marianopeck.wordpress.com

Jan. 16, 2016

Running processes at startup vs startUpList, which one first?

by Mariano Martinez Peck

Hi, I have a funny question. Let's say I did: [ something ] fork. and `something` never finishes and does not get GC. And I have a class that I registered in startup list. Which gets done first? the resume of the above process of the processing of the startup list? Thanks! -- Mariano http://marianopeck.wordpress.com

Jan. 16, 2016

Re: [Pharo-dev] How do you normally merge Git branches with Metadata-less GitFileTree?

by Mariano Martinez Peck

OK, thanks Thierry. BTW, thanks for all the help you have been giving me in the last weeks and for your great GitFileTree :) On Sat, Jan 16, 2016 at 11:14 AM, Thierry Goubier <thierry.goubier(a)gmail.com > wrote: > Le 16/01/2016 15:06, Mariano Martinez Peck a Ã©crit : > >> >> >> On Sat, Jan 16, 2016 at 5:15 AM, Thierry Goubier >> <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: >> >> Le 16/01/2016 03:23, Mariano Martinez Peck a Ã©crit : >> >> Hi guys, >> >> First, let me say that I found very cool that I can do a "git >> checkout >> X" from command line, and from Pharo, opening the MC browser >> detects I >> am in another branch and everything seems to work. So I guess >> that's the >> way I manage branches? Simply "git checkout X" and then go to MC >> , and >> do a "load" of the last version of the repo? (or another image, >> whatever). >> >> >> Yes, exactly. >> >> >> OK. >> >> >> >> The problem is now with merging. Not necessary about the >> metadata ( I >> guess we have less metadata conflicts with Metadata-less >> GitFileTree >> right???) , but real code changes conflicts between branches. >> How do you >> manage this? You manage everything at Git level using git and >> text editors? >> >> >> yes, or with git gui tools, or with the github interface (if there >> is no conflict). The only thing a bit problematic are the eventual >> conflicts, but, in that metadata-less format, they are less frequent >> and easier to solve. >> >> >> OK... but let me confirm... with metadata-less gitfiletree, would I >> still benefit from >> https://github.com/ThierryGoubier/GitFileTree-MergeDriver >> to minimize conflicts? >> Or that was when you were having filetree with metadata? >> > > The merge driver does three things: > - merge metadata version files > - merge method properties json files > - merge class definition json files (merge instances variables from both > branches) > > Items one and two do not exist anymore in metadata-less format. Third one > is not allways seen as a good thing. > > So the merge driver is rarely usefull in metadata-less mode. > > I cannot think how to do that from MC browser "Merge" because MC >> sees >> only one repo associated to one current branch. >> >> >> It is possible to do the merge in MC (think of merging your current >> working copy and the top of the branch) but they won't be recorded >> in the git log as a merge. >> >> >> OK. I prefer git to see it as a merge. But thanks anyway. >> > > I understand and do the same. Moreover, git is better than MC in my > opinion to do the merge properly. > > Thierry > > -- Mariano http://marianopeck.wordpress.com

Jan. 16, 2016

Re: [Pharo-dev] How do you normally merge Git branches with Metadata-less GitFileTree?

by Thierry Goubier

Le 16/01/2016 15:06, Mariano Martinez Peck a Ã©crit : > > > On Sat, Jan 16, 2016 at 5:15 AM, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > Le 16/01/2016 03:23, Mariano Martinez Peck a Ã©crit : > > Hi guys, > > First, let me say that I found very cool that I can do a "git > checkout > X" from command line, and from Pharo, opening the MC browser > detects I > am in another branch and everything seems to work. So I guess > that's the > way I manage branches? Simply "git checkout X" and then go to MC > , and > do a "load" of the last version of the repo? (or another image, > whatever). > > > Yes, exactly. > > > OK. > > > > The problem is now with merging. Not necessary about the > metadata ( I > guess we have less metadata conflicts with Metadata-less GitFileTree > right???) , but real code changes conflicts between branches. > How do you > manage this? You manage everything at Git level using git and > text editors? > > > yes, or with git gui tools, or with the github interface (if there > is no conflict). The only thing a bit problematic are the eventual > conflicts, but, in that metadata-less format, they are less frequent > and easier to solve. > > > OK... but let me confirm... with metadata-less gitfiletree, would I > still benefit from > https://github.com/ThierryGoubier/GitFileTree-MergeDriver > to minimize conflicts? > Or that was when you were having filetree with metadata? The merge driver does three things: - merge metadata version files - merge method properties json files - merge class definition json files (merge instances variables from both branches) Items one and two do not exist anymore in metadata-less format. Third one is not allways seen as a good thing. So the merge driver is rarely usefull in metadata-less mode. > I cannot think how to do that from MC browser "Merge" because MC > sees > only one repo associated to one current branch. > > > It is possible to do the merge in MC (think of merging your current > working copy and the top of the branch) but they won't be recorded > in the git log as a merge. > > > OK. I prefer git to see it as a merge. But thanks anyway. I understand and do the same. Moreover, git is better than MC in my opinion to do the merge properly. Thierry

Jan. 16, 2016

[pharo-project/pharo-core] 233d1c: 50529

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 233d1c603f211e85b5f990a062f4977faad8a57d https://github.com/pharo-project/pharo-core/commit/233d1c603f211e85b5f990a0… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-16 (Sat, 16 Jan 2016) Changed paths: M Rubric.package/RubScrolledTextMorph.class/instance/model protocol/drawHighlightsOn_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50528.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50529.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50528.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50529.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50529 17201 Marking Diffs broken in Pharo5 https://pharo.fogbugz.com/f/cases/17201 http://files.pharo.org/image/50/50529.zip

Jan. 16, 2016

[pharo-project/pharo-core]

by GitHub

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

Jan. 16, 2016

Re: [Pharo-dev] How do you normally merge Git branches with Metadata-less GitFileTree?

by Mariano Martinez Peck

On Sat, Jan 16, 2016 at 5:15 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Le 16/01/2016 03:23, Mariano Martinez Peck a Ã©crit : > >> Hi guys, >> >> First, let me say that I found very cool that I can do a "git checkout >> X" from command line, and from Pharo, opening the MC browser detects I >> am in another branch and everything seems to work. So I guess that's the >> way I manage branches? Simply "git checkout X" and then go to MC , and >> do a "load" of the last version of the repo? (or another image, >> whatever). >> > > Yes, exactly. OK. > > > The problem is now with merging. Not necessary about the metadata ( I >> guess we have less metadata conflicts with Metadata-less GitFileTree >> right???) , but real code changes conflicts between branches. How do you >> manage this? You manage everything at Git level using git and text >> editors? >> > > yes, or with git gui tools, or with the github interface (if there is no > conflict). The only thing a bit problematic are the eventual conflicts, > but, in that metadata-less format, they are less frequent and easier to > solve. > > OK... but let me confirm... with metadata-less gitfiletree, would I still benefit from https://github.com/ThierryGoubier/GitFileTree-MergeDriver to minimize conflicts? Or that was when you were having filetree with metadata? > I cannot think how to do that from MC browser "Merge" because MC sees >> only one repo associated to one current branch. >> > > It is possible to do the merge in MC (think of merging your current > working copy and the top of the branch) but they won't be recorded in the > git log as a merge. > > OK. I prefer git to see it as a merge. But thanks anyway. > Thierry > > > Any pointer is appreciated. >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > -- Mariano http://marianopeck.wordpress.com

Jan. 16, 2016

Can't gdb VM crash

by Mariano Martinez Peck

Hi guys, I build a Spur VM for debug, I tried to run an image that is crashing me on startup but all I get from gdb is: [Inferior 1 (process 1358) exited with code 01] (gdb) call printAllStacks() You can't do that without a process to debug. mmm I was always able to see stack traces. No I cannot do anything. Any ideas what could be wrong? I have no clue why it is failing at startup and I need to know it. Thanks in advance, -- Mariano http://marianopeck.wordpress.com

Jan. 16, 2016

Re: [Pharo-dev] Contributing to Pharo

by Stephan Eggermont

On 16-01-16 12:25, David Allouche wrote: > That does not make sense to me. I guess it will, when I understand Monticello better. Ideally, you start with the fresh, latest clean Pharo image to start working on an issue and make the changes in one go to create a slice. Then you only have to select the dirty packages. If the changes you are making risk killing the image, or there are simply a lot of them, you might commit intermediate steps where you detail your thought process/assumptions. The slice for the issue then can consist of packages that are already committed. Stephan

Jan. 16, 2016