May 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] MC Filetree -- missing FiletreeURL ?

by Frank Shearar

On 22 May 2013 12:13, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Le 22/05/2013 13:05, Frank Shearar a Ã©crit : > >> On 22 May 2013 12:05, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>> >>> I'm trying to setup a git-based build script from the command line and I >>> end >>> up unable to load a configuration from a filetree repository on the pharo >>> command line. >>> >>> Has someone encountered that? It seems Gopher is missing a FiletreeURL >>> for >>> this to work. >> >> >> What does your script currently look like? >> >> frank >> >> >> > ./pharo Pharo.image config filetree://`pwd`/../src/ > > Fails on trying to execute #mcRepositoryAsUser:withPassword: on a GenericUrl > instance inside Gofer. Yep, I'd agree with your assessment. Has Pharo forked Gofer, or does it still use Lukas Renggli's repository? frank

May 22, 2013

Re: [Pharo-dev] MC Filetree -- missing FiletreeURL ?

by Goubier Thierry

Le 22/05/2013 13:05, Frank Shearar a Ã©crit : > On 22 May 2013 12:05, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> I'm trying to setup a git-based build script from the command line and I end >> up unable to load a configuration from a filetree repository on the pharo >> command line. >> >> Has someone encountered that? It seems Gopher is missing a FiletreeURL for >> this to work. > > What does your script currently look like? > > frank > > > ./pharo Pharo.image config filetree://`pwd`/../src/ Fails on trying to execute #mcRepositoryAsUser:withPassword: on a GenericUrl instance inside Gofer. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

May 22, 2013

MC Filetree -- missing FiletreeURL ?

by Goubier Thierry

I'm trying to setup a git-based build script from the command line and I end up unable to load a configuration from a filetree repository on the pharo command line. Has someone encountered that? It seems Gopher is missing a FiletreeURL for this to work. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

May 22, 2013

Re: [Pharo-dev] MC Filetree -- missing FiletreeURL ?

by Frank Shearar

On 22 May 2013 12:05, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > I'm trying to setup a git-based build script from the command line and I end > up unable to load a configuration from a filetree repository on the pharo > command line. > > Has someone encountered that? It seems Gopher is missing a FiletreeURL for > this to work. What does your script currently look like? frank

May 22, 2013

Re: [Pharo-dev] [update 3.0] #30154

by Pavel Krivanek

https://pharo.fogbugz.com/f/cases/10720 On Wed, May 22, 2013 at 12:06 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com>wrote: > > > On Wed, May 22, 2013 at 10:24 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > >> >> On May 22, 2013, at 10:00 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> >> wrote: >> >> > Marcus, there are some problems with renamed Morphic package. In the >> Monticello packages list I see Morphic (MarcusDenker.1). >> > In the class PluggableMenuSpec there is a category named >> *Morphic-Menus, that now should be *Morphic-Base-Menus. So I guess this >> mess has origin in the Spec update integration. >> > >> > I think we should revert whole this update. >> >> So I retracted it. >> >> Now just *how* do I know that a SLICE is bad? It did not lead to a >> conflict, there is no way to realize that there is a problem. >> > > It is very strange that we had such problems with this update because all > of the slices do not modify Morphic package. > I think that the problem is in the act of renaming where extension of the > classes that are part of the renamed packages were not renamed. So maybe we > will not have such problems with later merges (but I'm not sure) > > -- Pavel > > > >> Marcus >> >> >> >

May 22, 2013

Re: [Pharo-dev] 3.0 git tracker

by Frank Shearar

On 22 May 2013 10:11, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-05-19, at 03:23, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> On 18 May 2013 02:31, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> Pharo 3.0 is now properly tracked on github >>> >>> - https://github.com/pharo-project/pharo-core >>> - the update messages are properly shown >>> - html output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4cc… >>> - diff output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4cc… >>> - patch output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4cc… >> >> You are my hero! >> Now can we have same for VM sources? >> I would really love to simplify a process of changing VM by simply modifying >> file either on disk (in platform sources) or in image (VMMaker & friends) >> and then do >> >> git ci -m "new fix/feature integrated" > > well it works only 1 way right now. I have not implemented any mapping from my fileformat > to monticello (even though it shouldn't be that hard). You could take a look at Filetree's reader (MCFileTreeStReader, IIRC). Your fileout format's pretty similar. frank

May 22, 2013

Re: [Pharo-dev] [update 3.0] #30154

by Pavel Krivanek

On Wed, May 22, 2013 at 10:24 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On May 22, 2013, at 10:00 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > > Marcus, there are some problems with renamed Morphic package. In the > Monticello packages list I see Morphic (MarcusDenker.1). > > In the class PluggableMenuSpec there is a category named *Morphic-Menus, > that now should be *Morphic-Base-Menus. So I guess this mess has origin in > the Spec update integration. > > > > I think we should revert whole this update. > > So I retracted it. > > Now just *how* do I know that a SLICE is bad? It did not lead to a > conflict, there is no way to realize that there is a problem. > It is very strange that we had such problems with this update because all of the slices do not modify Morphic package. I think that the problem is in the act of renaming where extension of the classes that are part of the renamed packages were not renamed. So maybe we will not have such problems with later merges (but I'm not sure) -- Pavel > Marcus > > >

May 22, 2013

Re: [Pharo-dev] [update 3.0] #30153

by Damien Cassou

On Tue, May 21, 2013 at 9:53 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > yes because nicolas should change the diff algorithem to diff against the latest present parent and not just the direct one since we merge. > I really want to get the diff working. advertisement: everyone can now work on SmalltalkHub: https://ci.inria.fr/pharo-contribution/job/SmalltalkHub -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

May 22, 2013

Re: [Pharo-dev] AST Everywhere, Reflectivity

by Denis Kudriashov

2013/5/22 Marcus Denker <marcus.denker(a)inria.fr> > > On May 22, 2013, at 11:23 AM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > > 2013/5/22 Frank Shearar <frank.shearar(a)gmail.com> > >> Why does ifTrue: use a compile-time transformation? > > > But what makes #future be similar to "ifTrue" case? What makes it so > special? > > > > And why do we discuss this on this Mailinglist? There are no Futures on > Pharoâ¦ > > Sorry for that. > Marcus > >

May 22, 2013

Re: [Pharo-dev] AST Everywhere, Reflectivity

by Marcus Denker

On May 22, 2013, at 11:23 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2013/5/22 Frank Shearar <frank.shearar(a)gmail.com> > Why does ifTrue: use a compile-time transformation? > > But what makes #future be similar to "ifTrue" case? What makes it so special? > And why do we discuss this on this Mailinglist? There are no Futures on Pharoâ¦ Marcus

May 22, 2013