February 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Using Metacello scripting API with non-github repo

by Paul DeBruicker

Oh. Hmm. Seems like the url for Metacello should point right to the "repository" directory in the git repo. so ssh://git@bitbucket.somehost.be:8899/xxx/t3-pharo/repository but when I use scp to copy a file over ssh I always have to add an extra colon (:) before the path, after the domain/port combo. So maybe its ssh://git@bitbucket.somehost.be:8899:/xxx/t3-pharo/repository Sven Van Caekenberghe-2 wrote > But it is not just private, it runs on our own servers. > > Maybe MCBitbucketRepository has to be extended like the MCGitlabRepository > as Cyril suggested ... > >> On 19 Feb 2019, at 19:08, Paul DeBruicker < > pdebruic@ > > wrote: >> >> Does >> >> Metacello>>#bitbucketUser:project:commitish: path: >> >> do what you want? >> >> >> You can set your bitbucket username/password with >> >> MCBitbucketRepository siteUsername: myUsername sitePassword: myPassword >> >> Which should let you access your private repo >> >> >> >> >> >> Sven Van Caekenberghe-2 wrote >>> Hi, >>> >>> My code lives in a private bitbucket git repo, how can I use this with >>> the >>> Metacello scripting API ? >>> >>> Metacello new >>> repository: 'ssh:// >> >>> git@.somehost >> >>> :8899/xxx/t3-pharo.git'; >>> baseline: 'BetaNineT3'; >>> load: #('core' 'gb'). >>> >>> IOW, what is the correct URL ? >>> >>> Is that even possible, if not what is the alternative ? >>> >>> I created/used this repo before, using keys as authentication. >>> >>> Could one also use username/password authentication, like when deploying >>> ? >>> >>> Sven >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 19, 2019

Re: [Pharo-dev] Using Metacello scripting API with non-github repo

by Sven Van Caekenberghe

But it is not just private, it runs on our own servers. Maybe MCBitbucketRepository has to be extended like the MCGitlabRepository as Cyril suggested ... > On 19 Feb 2019, at 19:08, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > > Does > > Metacello>>#bitbucketUser:project:commitish: path: > > do what you want? > > > You can set your bitbucket username/password with > > MCBitbucketRepository siteUsername: myUsername sitePassword: myPassword > > Which should let you access your private repo > > > > > > Sven Van Caekenberghe-2 wrote >> Hi, >> >> My code lives in a private bitbucket git repo, how can I use this with the >> Metacello scripting API ? >> >> Metacello new >> repository: 'ssh:// > >> git@.somehost > >> :8899/xxx/t3-pharo.git'; >> baseline: 'BetaNineT3'; >> load: #('core' 'gb'). >> >> IOW, what is the correct URL ? >> >> Is that even possible, if not what is the alternative ? >> >> I created/used this repo before, using keys as authentication. >> >> Could one also use username/password authentication, like when deploying ? >> >> Sven > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 19, 2019

Re: [Pharo-dev] Question on KmGlobalDispatcher

by ducasse

Hello David Indeed this is a good catch. Can you open a bug entry on github? Else I will do it but this is cool to get involved that way > On 19 Feb 2019, at 17:37, David Richards <david.i.richards.iii(a)gmail.com> wrote: > > Why does the class name KmGlobalDispatcher have a small 'm'? > > Should it be more consistently named KMGlobalDispatcher, as all other classes in package: 'Keymapping-Core'? > > Object subclass: #KmGlobalDispatcher > instanceVariableNames: 'dispatcher' > classVariableNames: '' > package: 'Keymapping-Core' > > Just curious why this name seems inconsistent. I don't recall seeing an inconsistency with class name prefixes in any other package group. Is this just a mistake, or rather an opportunity to learn something interesting about how classes should be named in Pharo? As a beginner, I'm not sure which. > > Thanks > David

Feb. 19, 2019

Re: [Pharo-dev] Using Metacello scripting API with non-github repo

by Paul DeBruicker

Does Metacello>>#bitbucketUser:project:commitish: path: do what you want? You can set your bitbucket username/password with MCBitbucketRepository siteUsername: myUsername sitePassword: myPassword Which should let you access your private repo Sven Van Caekenberghe-2 wrote > Hi, > > My code lives in a private bitbucket git repo, how can I use this with the > Metacello scripting API ? > > Metacello new > repository: 'ssh:// > git@.somehost > :8899/xxx/t3-pharo.git'; > baseline: 'BetaNineT3'; > load: #('core' 'gb'). > > IOW, what is the correct URL ? > > Is that even possible, if not what is the alternative ? > > I created/used this repo before, using keys as authentication. > > Could one also use username/password authentication, like when deploying ? > > Sven -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 19, 2019

Question on KmGlobalDispatcher

by David Richards

Why does the class name KmGlobalDispatcher have a small 'm'? Should it be more consistently named KMGlobalDispatcher, as all other classes in package: 'Keymapping-Core'? Object subclass: #KmGlobalDispatcher instanceVariableNames: 'dispatcher' classVariableNames: '' package: 'Keymapping-Core' Just curious why this name seems inconsistent. I don't recall seeing an inconsistency with class name prefixes in any other package group. Is this just a mistake, or rather an opportunity to learn something interesting about how classes should be named in Pharo? As a beginner, I'm not sure which. Thanks David

Feb. 19, 2019

Re: [Pharo-dev] Using Metacello scripting API with non-github repo

by Cyril Ferlicot

On Tue, Feb 19, 2019 at 2:57 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > My code lives in a private bitbucket git repo, how can I use this with the Metacello scripting API ? > > Metacello new > repository: 'ssh://git@bitbucket.somehost.be:8899/xxx/t3-pharo.git'; > baseline: 'BetaNineT3'; > load: #('core' 'gb'). > > IOW, what is the correct URL ? > > Is that even possible, if not what is the alternative ? > > I created/used this repo before, using keys as authentication. > > Could one also use username/password authentication, like when deploying ? Hi, I think non default ssh port will not be supported by Metacello. I had to add it for gitlab to be able to reference repositories from a self hosted gitlab with non default ssh port. I guess the same can be done for bitbucket but it I doub it's already done. For Gitlab I added it in MCGitlabRepository for the Metacello part and in the Iceberg extensions of this class to use the new infos in Iceberg. (Method scpUrl) > > Sven > > > -- Cyril Ferlicot https://ferlicot.fr

Feb. 19, 2019

Re: [Pharo-dev] Using Metacello scripting API with non-github repo

by Sven Van Caekenberghe

I can add that Iceberg _can_ clone from my URL, it just seems that Metacello doesn't understand it. > On 19 Feb 2019, at 14:56, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > My code lives in a private bitbucket git repo, how can I use this with the Metacello scripting API ? > > Metacello new > repository: 'ssh://git@bitbucket.somehost.be:8899/xxx/t3-pharo.git'; > baseline: 'BetaNineT3'; > load: #('core' 'gb'). > > IOW, what is the correct URL ? > > Is that even possible, if not what is the alternative ? > > I created/used this repo before, using keys as authentication. > > Could one also use username/password authentication, like when deploying ? > > Sven > >

Feb. 19, 2019

Using Metacello scripting API with non-github repo

by Sven Van Caekenberghe

Hi, My code lives in a private bitbucket git repo, how can I use this with the Metacello scripting API ? Metacello new repository: 'ssh://git@bitbucket.somehost.be:8899/xxx/t3-pharo.git'; baseline: 'BetaNineT3'; load: #('core' 'gb'). IOW, what is the correct URL ? Is that even possible, if not what is the alternative ? I created/used this repo before, using keys as authentication. Could one also use username/password authentication, like when deploying ? Sven

Feb. 19, 2019

[Pharo 8.0] Build #91: Remove DebugSession>>activePC: and DebugSessio>>previousPC:

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #91 was: FAILURE. The Pull Request #2653 was integrated: "Remove DebugSession>>activePC: and DebugSessio>>previousPC:" Pull request url: https://github.com/pharo-project/pharo/pull/2653 Issue Url: https://pharo.fogbugz.com/f/cases/2274 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 19, 2019

Re: [Pharo-dev] [Pharo-users] About Iceberg

by Tim Mackinnon

Yes I agree - when there is so much discussion and debate going on, its easy to lose sight of the hard work and determination that went into getting us to this brave new world. I too want to shout a big thank you for the tooling and also the support that goes along with that. I love been able to think a bit more polyglot, and use tools/languages more easily side by side - although of course I want to hold on to what makes Smalltalk special (which is tons of stuff). I particularly love being able to feel like its easier to contribute - updating readmeâs and docs is trivial in a web browser now - just correct them and submit a PR. And on the receiving side - GitHub makes it easy to discuss the fix, alter it, or simply approve it. Equally - modern build tools easily detect the change, pull the code and rebuild and package it (and cheap scalable infrastructure). Its also getting easier and easier to submit code fixes too - and the VCS skills you learn doing this are transferable beyond Smalltalk - so its a big win win. So yes guys - thanks for hanging in for us! Tim > On 19 Feb 2019, at 08:50, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > This is a thank you note about Iceberg. > > I have been moving all my external and internal Pharo code to git/tonel/7 and on multiple occasions I have been pleasantly surprised about the functionality and performance of Iceberg. Basically, it just works. > > Finally, Pharo code lives in standard open source and commercial repositories (git, GitHub, Bitbucket, ...), without losing anything. > > I know that it took years to get here and that lots of code and community battles had to be fought. So thank you, to the whole team, you did a great job ! > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

Feb. 19, 2019