- Pharo-dev - lists.pharo.org

cog svn tracker setup

by Camillo Bruni

I spent some time setting up a git tracker for the cog svn repository. This should help us reducing the merge errors for the pharo-vm, when picking changes from eliot's branch on http://squeakvm.org/svn/squeak/branches/Cog It takes a prepared zip with the proper meta information for git-svn from here http://files.pharo.org/vm/src/cog-git-svn-track.zip and updates the separate repositories from the github squeakvm project http://github.com/squeakvm/ Currently this is a very fragile setup, since git and svn:externals are not very compatible. However, it does the trick for our purposes. The following steps are run on a daily basis: --------------------------------------------- https://ci.inria.fr/pharo/view/Helper/job/Cog-SVN-Tracker/ 1. update both of the commonly shared plugin directories 2. fetch on the latest svn version on the 'svn' for cog 3. load the plugin repositories in with 'git subtree' on the 'master' branch on cog 4. merge the 'master' branch with the 'svn' branch 5. push Steps to do ----------- - setup a proper mergepoint somewhere in the past of pharo-vm (that requires git black magic) - pharo-vm has to merge with the latest changes from cog (that requires VM knowledge)

Oct. 8, 2013

Re: [Pharo-dev] Pharo Sprint Lille 18th October

by StÃ©phane Ducasse

me if necessary :) On Oct 8, 2013, at 7:34 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > Who will spend its day integrating fixes ? (If not Marcus) > > > 2013/10/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > 06 30 93 66 73 in case of problem > > stef > > On Oct 8, 2013, at 5:08 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > > On Oct 8, 2013, at 4:07 PM, phil(a)highoctane.be wrote: > > > >> Booking the date right away. > >> > >> Is the best course of action to register in the other building and then crossing the road with someone picking me up? > > > > Maybe that is the bestâ¦ I will not be here the 18th, so I can't give you my cellphone number. > > > > Marcus > > > > >

Oct. 8, 2013

Re: [Pharo-dev] Pharo Sprint Lille 18th October

by ClÃ©ment Bera

Who will spend its day integrating fixes ? (If not Marcus) 2013/10/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > 06 30 93 66 73 in case of problem > > stef > > On Oct 8, 2013, at 5:08 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > > On Oct 8, 2013, at 4:07 PM, phil(a)highoctane.be wrote: > > > >> Booking the date right away. > >> > >> Is the best course of action to register in the other building and then > crossing the road with someone picking me up? > > > > Maybe that is the bestâ¦ I will not be here the 18th, so I can't give you > my cellphone number. > > > > Marcus > > > > >

Oct. 8, 2013

Re: [Pharo-dev] Pharo Sprint Lille 18th October

by Esteban A. Maringolo

Unfortunately Lille is too far from Paris, because I'll be in Paris from Oct. 18th to 23rd. :-/ Esteban A. Maringolo 2013/10/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > 06 30 93 66 73 in case of problem > > stef > > On Oct 8, 2013, at 5:08 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > > On Oct 8, 2013, at 4:07 PM, phil(a)highoctane.be wrote: > > > >> Booking the date right away. > >> > >> Is the best course of action to register in the other building and then > crossing the road with someone picking me up? > > > > Maybe that is the bestâ¦ I will not be here the 18th, so I can't give you > my cellphone number. > > > > Marcus > > > > >

Oct. 8, 2013

Re: [Pharo-dev] Pharo Sprint Lille 18th October

by StÃ©phane Ducasse

06 30 93 66 73 in case of problem stef On Oct 8, 2013, at 5:08 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Oct 8, 2013, at 4:07 PM, phil(a)highoctane.be wrote: > >> Booking the date right away. >> >> Is the best course of action to register in the other building and then crossing the road with someone picking me up? > > Maybe that is the bestâ¦ I will not be here the 18th, so I can't give you my cellphone number. > > Marcus >

Oct. 8, 2013

Re: [Pharo-dev] Pharo Sprint Lille 18th October

by Marcus Denker

On Oct 8, 2013, at 4:07 PM, phil(a)highoctane.be wrote: > Booking the date right away. > > Is the best course of action to register in the other building and then crossing the road with someone picking me up? Maybe that is the bestâ¦ I will not be here the 18th, so I can't give you my cellphone number. Marcus

Oct. 8, 2013

Re: [Pharo-dev] Pharo Sprint Lille 18th October

by StÃ©phane Ducasse

+1 On Oct 8, 2013, at 4:11 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-10-08, at 16:06, phil(a)highoctane.be wrote: > >> Booking the date right away. >> >> Is the best course of action to register in the other building and then >> crossing the road with someone picking me up? >> >> Wouldn't it be a good thing to look at Fogbugz issues and close what can >> be? Boring tasks but could benefit from the Sprint energy boost! > > yes, the more boring the better for the spring, since these bugs tend to not > be fixed :P

Oct. 8, 2013

Re: [Pharo-dev] external semaphoresâ¦again

by StÃ©phane Ducasse

> > i agree. i will create a bug entry for it then.. thanks Igor how could we write a test that make sure that your changes are not unrolled unnotified? Stef

Oct. 8, 2013

Re: [Pharo-dev] About Soup and XML

by StÃ©phane Ducasse

Hi paul > Hi stef > > I copied the XMLSupport project from squeaksource because I thought > squeaksource.com was going to go away. Now that it is not I'm totally fine > using it, like we have in the past. Sorry to be sttuborn but I do not have the time not to be :) For me Squeaksource is dead because this is not because it will run that it will not lose files on reboot and others. So I will not use Squeaksource for anything that I maintain. For me having squeaksource read only is good enough but this is not ready for my production code. Stef > I'll update the config now. > > > Thanks > > Paul > > > StÃ©phane Ducasse wrote >> Hi paul >> >> I do not think that it is wise in the long term to have split repository. >> For example it does not really make >> sense to me to have a part of XMLSupport in your private project and >> another part in squeaksource. >> So we should >> - update soup to use XMLReader in SmalltalkHub >> - and publish gemstone package in their corresponding base project >> >> Managing conifguration is complex enough to make things as simple as we >> can. >> So are you interested in helping? >> >> Stef >> >> >> baseline14: spec >> >> <version: '1.4-baseline'> >> spec >> for: #squeakCommon >> do: [ >> spec blessing: #baseline. >> spec description: 'Migrated to SmalltalkHub'. >> spec author: 'StephaneDucasse'. >> spec timestamp: '21/02/2013'. >> spec repository: >> 'http://www.smalltalkhub.com/mc/PharoExtras/Soup/main'. >> spec >> package: 'Soup-Core' with: [ spec requires: 'XMLSupport' ]; >> package: 'Soup-Tests-Core' with: [ spec requires: 'Soup-Core' ]; >> package: 'Soup-Help' with: [ spec requires: 'Soup-Core' ]; >> package: 'Soup-XPath' with: [ spec requires: 'Soup-Core' ]; >> package: 'Soup-Zinc' with: [ spec requires: 'Soup-Core' ]. >> spec >> project: 'XMLSupport' >> with: [ spec >> className: 'ConfigurationOfXMLSupport'; >> versionString: #stable; >> repository: 'http://www.squeaksource.com/XMLSupport' ]. >> spec >> group: 'default' with: #('Core' 'Tests'); >> group: 'Core' with: #('Soup-Core' 'Soup-XPath'); >> group: 'Tests' with: #('Soup-Tests-Core') ]. >> spec >> for: #gemstone >> do: [ >> spec repository: >> 'http://www.smalltalkhub.com/mc/PharoExtras/Soup/main'. >> spec >> project: 'XMLSupport' >> with: [ spec >> className: 'ConfigurationOfXMLSupport'; >> versionString: #stable; >> repository: >> 'http://www.smalltalkhub.com/mc/pdebruic/XMLSupport/main' ]. >> spec >> package: 'SoupGemstone-Core' with: [ spec requires: 'XMLSupport' ]; >> package: 'Soup-Tests-Core' with: [ spec requires: 'SoupGemstone-Core' >> ]; >> package: 'Soup-Help' with: [ spec requires: 'SoupGemstone-Core' ]; >> package: 'Soup-XPath' with: [ spec requires: 'SoupGemstone-Core' ]; >> package: 'Soup-Zinc' with: [ spec requires: 'SoupGemstone-Core' ]. >> >> spec >> group: 'default' with: #('Core' 'Tests'); >> group: 'Core' with: #('SoupGemstone-Core'); >> group: 'Tests' with: #('Soup-Tests-Core') ]. > > > > > > -- > View this message in context: http://forum.world.st/About-Soup-and-XML-tp4711421p4713095.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Oct. 8, 2013

Re: [Pharo-dev] about creating Morphic-Widgets

by StÃ©phane Ducasse

So will propose a slice with that to get moving. On Oct 6, 2013, at 8:54 PM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > Hi guys > > I started to play with sorting a bit Morphic :) > So I would like to create a new Package Morphics-Widgets with the following contents. > > > Morphic-Widgets-Basic > SimpleSwitchMorph > MulticolumnLazyListMorph > SimpleButtonMorph > LazyListMorph > IconicButton > ThreePhaseButtonMorph > CalendarMorph > Morphic-Widgets-Pluggable > PluggableTabButtonMorph > PluggableButtonMorph > PluggableTextMorph > PluggableMultiColumnListMorph > PluggableTextMorphWithLimits > PluggableTabBarMorph > PluggableListMorph > Morphic-Widgets-NewList > NewList > NewListRenderer > NewListAdapter > Morphic-Widgets-Tab > > Morphic-Widget-MorphTreeWidget > Morphic-Widget-MorphTreeWidget-Pagination > > I would promote Morphic-Base-ProgressBar -> Morphic-ProgressBar > > So what do you think? > >

Oct. 8, 2013