March 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] GitHub: Easiest Way to Load a Project (update)

by Thierry Goubier

Le 07/03/2015 20:10, Sven Van Caekenberghe a Ã©crit : > >> On 07 Mar 2015, at 19:41, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >> >> For example, the following would work : >> >> Gofer it >> url: 'gitfiletree://github.com/rohitsukhwal/HelloWorld.git?protocol=git'; >> package: 'HelloWorld'; >> load >> >> Adding that type of Url in both Gofer and Metacello requires overrides in Zn and Metacello: ugly :(:( > > I created an issue to study what (if anything) has to change to ZnUrl in order to help here: > > https://pharo.fogbugz.com/f/cases/15090/ZnUrl-should-be-able-to-better-supp… Thanks. > However, the parsing works fine & correct: > > 'gitfiletree://github.com/rohitsukhwal/HelloWorld.git?protocol=git' asZnUrl > > which leads me to suspect the problem is in usage. Well, I use ZnUrl to decode gitfiletree: urls, so I'm sure I choose a correct url scheme :) The only extension needed is the dispatch on the scheme of the url: what ZnUrl can dispatch is hardcoded as a case switch. Thierry

March 7, 2015

Re: [Pharo-dev] GitHub: Easiest Way to Load a Project (update)

by Thierry Goubier

Le 07/03/2015 20:12, Sean P. DeNigris a Ã©crit : > > > Thierry Goubier wrote >> Your snippet (with corrected package name ;)) was just what I was looking >> for: >> Gofer it >> url: 'gitfiletree://github.com/rohitsukhwal/HelloWorld.git?protocol=git'; >> package: 'My-Spec-Tutorial'; >> load > > I may have spoken a tiny bit too soon. Why does the above snippet create a > local filetree repo instead of a remote git repo like the following? > MCFileTreeGitRemoteRepository > location: 'git@github.com:rohitsukhwal/HelloWorld.git' > name: 'sean' > subdirectory: '' > branch: ''. Both are one and the same, but created via two different approaches. MCFileTreeGitRepository knows how to both link to an on-disk repo (local gitfiletree url) and to clone a remote repository... But the Monticello GUI only allow one type of creation per class of repository. So if a MCFileTreeGitRepository addition in the MC GUI opens a file dialog to select a local directory, you need another class (the MCFileTreeGitRemoteRepository) to allow you to enter the description of a remote git repository at addition. ... Thierry

March 7, 2015

Re: [Pharo-dev] GitHub: Easiest Way to Load a Project (update)

by Thierry Goubier

Le 07/03/2015 20:10, Peter UhnÃ¡k a Ã©crit : > I ended up pushing to GitHub via the command line. Is there a way to > do it > from within the image? > > If you open the repository through Monticello Browser there are buttons > 'Pull' and 'Push'. I've never tried them, but they should probably work. They should work :). 'Pull' will do a git pull --rebase, 'Push' will do a push and be active only if there is something to push. Thierry

March 7, 2015

Re: [Pharo-dev] GitHub: Easiest Way to Load a Project (update)

by Sean P. DeNigris

Thierry Goubier wrote > Your snippet (with corrected package name ;)) was just what I was looking > for: > Gofer it > url: 'gitfiletree://github.com/rohitsukhwal/HelloWorld.git?protocol=git'; > package: 'My-Spec-Tutorial'; > load I may have spoken a tiny bit too soon. Why does the above snippet create a local filetree repo instead of a remote git repo like the following? MCFileTreeGitRemoteRepository location: 'git@github.com:rohitsukhwal/HelloWorld.git' name: 'sean' subdirectory: '' branch: ''. ----- Cheers, Sean -- View this message in context: http://forum.world.st/GitHub-Easiest-Way-to-Load-a-Project-update-tp4810309… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 7, 2015

Re: [Pharo-dev] GitHub: Easiest Way to Load a Project (update)

by Sven Van Caekenberghe

> On 07 Mar 2015, at 19:41, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > For example, the following would work : > > Gofer it > url: 'gitfiletree://github.com/rohitsukhwal/HelloWorld.git?protocol=git'; > package: 'HelloWorld'; > load > > Adding that type of Url in both Gofer and Metacello requires overrides in Zn and Metacello: ugly :(:( I created an issue to study what (if anything) has to change to ZnUrl in order to help here: https://pharo.fogbugz.com/f/cases/15090/ZnUrl-should-be-able-to-better-supp… However, the parsing works fine & correct: 'gitfiletree://github.com/rohitsukhwal/HelloWorld.git?protocol=git' asZnUrl which leads me to suspect the problem is in usage. Sven

March 7, 2015

Re: [Pharo-dev] GitHub: Easiest Way to Load a Project (update)

by Peter UhnÃ¡k

> > I ended up pushing to GitHub via the command line. Is there a way to do it > from within the image? > If you open the repository through Monticello Browser there are buttons 'Pull' and 'Push'. I've never tried them, but they should probably work. Peter

March 7, 2015

Re: [Pharo-dev] Delay issues

by Thierry Goubier

Hi Max, on another Ubuntu 14.10 machine, I have no issue as well. I'm starting to suspect an ubuntu upgrade effect on one of the system libs or the kernel. Would you have the time to see where one of those tests fail? Any one would probably tell me something. Thierry Le 07/03/2015 18:07, Max Leske a Ã©crit : > >> On 06 Mar 2015, at 17:21, Thierry Goubier <thierry.goubier(a)gmail.com >> <mailto:thierry.goubier@gmail.com>> wrote: >> >> >> >> 2015-03-06 16:17 GMT+01:00 Max Leske <maxleske(a)gmail.com >> <mailto:maxleske@gmail.com>>: >> >>> >>>> On 06 Mar 2015, at 16:08, Thierry Goubier >>>> <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> >>>> wrote: >>>> >>>> >>>> >>>> 2015-03-06 15:43 GMT+01:00 Max Leske <maxleske(a)gmail.com >>>> <mailto:maxleske@gmail.com>>: >>>> >>>> >>>>> On 06 Mar 2015, at 15:35, Thierry Goubier >>>>> <thierry.goubier(a)gmail.com >>>>> <mailto:thierry.goubier@gmail.com>> wrote: >>>>> >>>>> >>>>> >>>>> 2015-03-06 15:21 GMT+01:00 Max Leske <maxleske(a)gmail.com >>>>> <mailto:maxleske@gmail.com>>: >>>>> >>>>> >>>>>> On 06 Mar 2015, at 14:56, Thierry Goubier >>>>>> <thierry.goubier(a)gmail.com >>>>>> <mailto:thierry.goubier@gmail.com>> wrote: >>>>>> >>>>>> Ok. It's not an image problem. It seems to be a vm >>>>>> problem or an ubuntu problem. >>>>>> >>>>>> (vm and vmLatest from get.pharo.org >>>>>> <http://get.pharo.org/> have that, the vm in the pharo >>>>>> launcher seems to work fine, and I haven't seen any >>>>>> problem with Pharo3 ? Ubuntu 14.10 64bits). >>>>>> >>>>> >>>>> Ok, so we need to find the VM version that breaks >>>>> OSProcessâ¦ >>>>> >>>>> >>>>> I tried to rebuilt a vm from the git for pharo-vm, and it >>>>> failed at the end of the process... lots of incorrect >>>>> function redefinitions in cogit.c, if it says anything. >>>> >>>> Yes, I know that. Itâs a problem with gcc. To fix it and get >>>> a working VM you can use the following: >>>> >>>> /* pre-empty some preprocessor variables used in >>>> srv/vm/cogit.h, cointer.h, etc */ >>>> # define NoDbgRegParms >>>> # define NeverInline >>>> >>>> >>>> In which header do you add that? >>> >>> >>> src/vm/cogit.h >>> src/vm/cointerp.h >> >> and src/vm/gcc3x-cointerp.c >> >> >> Thanks, it worked. For the compilation, I mean. (the two .h happily >> contain code to define those two macros ??) >> >> Ok, conclusion with a brand new VM: stuck at the very first test. The >> worst result of all :( >> >> Thierry > > > I ran your tests a couple of times and didnât see any hangs or crashes > (although most of the tests failed). This is on OSX 10.10.2. > > output: > > 'Running tests in 1 Packages' > MCGitFileTreeIssue139Test>>#testWrite > [FAIL] > MCGitFileTreeIssue139Test>>#testLoad > [FAIL] > MCGitFileTreeIssue139Test>>#testWriteNRead > [FAIL] > MCGitFileTreeIssue139Test>>#testRepository > [FAIL] > MCGitFileTreeIssue146Test>>#testWrite > [FAIL] > MCGitFileTreeIssue146Test>>#testWriteNRead > [FAIL] > MCGitFileTreeIssue147Test>>#testWriteNRead > [FAIL] > MCGitFileTreeIssue26Test>>#testWriteNRead2 > [FAIL] > MCGitFileTreeIssue26Test>>#testWrite > [FAIL] > MCGitFileTreeIssue26Test>>#testLoad > [FAIL] > MCGitFileTreeIssue26Test>>#testWriteNRead > [FAIL] > MCGitFileTreeIssue33Test>>#testWrite > [FAIL] > MCGitFileTreeIssue33Test>>#testLoad > [FAIL] > MCGitFileTreeIssue33Test>>#testWriteNRead > [FAIL] > MCGitFileTreeIssue33Test>>#testRepository > [FAIL] > MCGitFileTreeIssue69Test>>#testLoad > [FAIL] > MCGitFileTreeIssue72Test>>#testLoad > [FAIL] > MCGitFileTreeIssue72Test>>#testWriteNRead > [FAIL] > MCGitFileTreeLoaderTest>>#testBaseLoadRepository > [FAIL] > MCGitFileTreeLoaderTest>>#testCypressCuisLoad > [FAIL] > MCGitFileTreeLoaderTest>>#testIssue74 > [FAIL] > MCGitFileTreeLoaderTest>>#testTargetLoad > [FAIL] > MCGitFileTreeLoaderTest>>#testTargetLoadRepository > [FAIL] > MCGitFileTreeLoaderTest>>#testBaseLoad > [FAIL] > MCGitFileTreeLoaderTraitsTest>>#testLoad > [FAIL] > MCGitFileTreeTests>>#testStoreReadGitFileTree > [31/31] > Finished running 31 Tests

March 7, 2015

Re: [Pharo-dev] GitHub: Easiest Way to Load a Project (update)

by Sean P. DeNigris

Thierry Goubier wrote > In Gofer or Monticello, you can use those Urls. > ... > I'm not sure I'd like to see all the relevant gofer methods: Agreed! I didn't know there was any Gofer support. Your snippet (with corrected package name ;)) was just what I was looking for: Gofer it url: 'gitfiletree://github.com/rohitsukhwal/HelloWorld.git?protocol=git'; package: 'My-Spec-Tutorial'; load I ended up pushing to GitHub via the command line. Is there a way to do it from within the image? ----- Cheers, Sean -- View this message in context: http://forum.world.st/GitHub-Easiest-Way-to-Load-a-Project-update-tp4810309… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 7, 2015

Re: [Pharo-dev] GitHub: Easiest Way to Load a Project (update)

by Thierry Goubier

Hi Sean, Le 07/03/2015 18:46, Sean P. DeNigris a Ã©crit : > There was a similar thread from 2013. I wonder what's changed... > > The method I cobbled together from various threads was: > 1. Load GitFileTree (available in the Config Browser in 3.0) > 2. In MC Browser, '+Repository' -> 'Remote git repository': > MCFileTreeGitRemoteRepository > location: 'git@github.com:rohitsukhwal/HelloWorld.git' > name: 'whatever' > subdirectory: '' > branch: '' > > A few questions: > 1. name: 'whatever' seems weird. I put 'whatever' because its only > significance seems to be the directory to which the repo gets cloned (i.e. > imageDirectory/whatever). I assume I'm missing something... Yes, name is not that clear. It's the name for the local repository, and I've set it so that you can work on two branches of the same repository (for example while developping filetree, work on the pharo3.0_dev and the pharo4.0_dev branches). This was to be able to merge between the two branches via MC... It was a bad idea, and its now useless due to the Merge Driver. > 2. The following also successfully cloned the repo, but would not be > accepted in MC Browser's add repo template dialog... MCFileTreeGitRepository > fromZnUrl: (ZnUrl fromString: > 'gitfiletree://github.com/rohitsukhwal/HelloWorld.git?protocol=git'). > a) How should it be used, or not? In Gofer or Monticello, you can use those Urls. For example, the following would work : Gofer it url: 'gitfiletree://github.com/rohitsukhwal/HelloWorld.git?protocol=git'; package: 'HelloWorld'; load Adding that type of Url in both Gofer and Metacello requires overrides in Zn and Metacello: ugly :(:( > b) Why does it clone into imageDirectory/gitHubProjectName, where #1 above > clones into ./name? See above about the use of 'name'... > 3. Since Metacello can apparently load from GitHub already, for write-only > repos, can that functionality be pushed into MC to be used e.g. with Gofer? > The method I found seems like a lot to ask, especially e.g. if you want > someone to take a quick look at a toy project with no Metacello config Well, you already have the support of the GitFileTree urls in Gofer, which helps for those cases (say that protocol is https for a read-only, very fast clone with --depth=1) > Ideally, as mentioned in the 2013 thread, it would be great to have: > Gofer it > gitHubUser: user project: project; But load what? > load The main goal of GitFileTree is supporting more than github (or bitbucket): gitorious, gitlab, notabug, etc... In my opinion, Metacello + Baseline on any git repository solve the problem elegantly enough, and I'm not sure I'd like to see all the relevant gofer methods: bibucketUser:project: gitlabUser:project: (gitorious is gone...) notabugUser:project: Not forgetting that you usually want to specify the branch as well. Thierry

March 7, 2015

Re: [Pharo-dev] GitHub: Easiest Way to Load a Project (update)

by Peter UhnÃ¡k

> > with no config > Since tags and branches are handled by git and not metacello, with Baseline you need just single method BaselineOfX>>baseline: see for example https://github.com/dalehenrich/filetree/blob/gemstone2.4/repository/Baselin… or https://github.com/dynacase/dynacase/blob/master/repository/BaselineOfDynaC… But of course this may not apply for your specific use case. Peter

March 7, 2015