June 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Loading Local Repositories with Iceberg

by Norbert Hartl

> Am 05.06.2018 um 16:13 schrieb Stephan Eggermont <stephan(a)stack.nl>: > > Norbert Hartl <norbert(a)hartl.name> wrote: > >> Ok, but where is the problem? > > - needs to work on different filesystems, with tricky behavior > - git itself did not get the behavior right > - git used to be non-reentrant. Did that change? > Ok, now we know about problems git should solve. What should we be doing? Norbert

June 5, 2018

Re: [Pharo-users] Loading Local Repositories with Iceberg

by Stephan Eggermont

Norbert Hartl <norbert(a)hartl.name> wrote: > Ok, but where is the problem? - needs to work on different filesystems, with tricky behavior - git itself did not get the behavior right - git used to be non-reentrant. Did that change? Stephan

June 5, 2018

Re: [Pharo-users] need help loading third-party packages

by Serge Stinckwich

In order to load the Citezen package, you can use the Catalog. Open Tools >> catalog browser and select Citezen package in order to load it. On Tue, Jun 5, 2018 at 6:14 AM Gregg Williams <gregg13(a)innerpaths.net> wrote: > Hi--another question, this time on loading an external package into Pharo. > > I want to do some work manipulating text, so I thought I would start by > reading the source code for an existing package that works on text. > > Here's what I did: > > On smalltalkhub.com, I found a package called Citezen, from team RMoD, > and downloaded the .mcz file. There were many versions, so I downloaded the > one with the latest timestamp. It helped that its name was > Citezen-All-sd20.mcz. > > I've tried adding this to my current Pharo 6.1 image in two ways: 1) by > dropping the .mcz file onto the window of PharoLauncher, and 2) moving the > file into my computer's package-cache directory. I had roughly the same > problems with both. > > Problem 1: There were multiple options for telling the system what do to > with it: Load, Load Version, Merge version, Open version, and Extract all > to.... > > Problem 2: Once I do that, I get to a window with buttons at the top: > Browse, History, Changes, Load, Merge, Adopt, Copy, Diff. > > Problem 3: Once I chose one of these, I got at least a half-dozen "Can't > find dependency <filename> Ignore?" messages (for example > "...Citezen-Parsers-cdlm.13" and "...Citezen-Tests-sd.39"). The default > button for this was "Yes", so I chose this. > > This started some downloading of files, a process that sometimes got > "stuck" and never completed. > > Not knowing any better, I then launched Pharo 6.1 (Stable). I could see no > indication that Citezen had been "added" to the system. > > Anyway, in a system browser, I searched for the string "Citezen" and found > five Citezen packages: All, Model, PArsers, Rendering, and Tests. But when > I selected any of them, no content appeared in the Class pane. Also > searching for a class containing "Cite" found nothing. > > Surely, other beginners have had the same problem as me. I would > appreciate pointers to any existing resources that would help me out, or > whatever help you'd care to give me. > > TO RECAP, I want to load third-party packages and read their source code. > What's the best way to do this? > > Many thanks! > > > -- Serge Stinckwich UMI UMMISCO 209 (SU/IRD/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/

June 5, 2018

Re: [Pharo-users] Loading Local Repositories with Iceberg

by Guillermo Polito

On Tue, Jun 5, 2018 at 8:20 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > > Am 04.06.2018 um 15:59 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > > > hi, > > > >> On 4 Jun 2018, at 12:57, Stephan Eggermont <stephan(a)stack.nl> wrote: > >> > >> Evan Donahue <emdonahu(a)gmail.com> wrote: > >>> I have "Share repositories between images" checked in both images, > >> > >> Share repositories at the moment just provides a shared location on disk > >> where the repositories are located. That is only useful if you are very > >> disciplined about stashing and switching to the branch needed for your > >> current image, and you only have one image open at a time. > > > > not really. > > P7 will force you to be in the right branch or you will not be able to > doâ¦ almost anything :) > > you can have two (or ten) images opened at once and work on them, but at > a moment you will need to ârepairâ each image to commit. > > > How does this work if the other image has updated the git index? Iceberg ignores completely git's index (until the moment you commit). I cannot tell it 100% sure but It probably depends on the particular scenario you're on but IIRC: - if you checkout with iceberg, it will most surely discard your index; - if you try to commit with iceberg and you have a dirty index, iceberg will commit coming from your image along with the thing in the index > Repairing will update&merge, too? What the merge operation does depends on the kind of merge: - a fast forward will just checkout the new commit in disk, probably discarding your index - a non fast forward will leave the disk as is, without touching the index (until you resolve the conflicts and then Iceberg will commit, which should do what I explained above) > That is usually the reason I commit always first so I commit to a prior > version of the index in order to have git merge on update. > Yes, I'd recommend people to try to have a clean working copy when using iceberg, and specially a clean index. > > Norbert > > Esteban > > > >> > >> Stephan > >> > >> > >> > >> > >> > > > > > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

June 5, 2018

Re: [Pharo-users] Loading Local Repositories with Iceberg

by Norbert Hartl

> Am 05.06.2018 um 09:03 schrieb Stephan Eggermont <stephan(a)stack.nl>: > > Norbert Hartl <norbert(a)hartl.name> wrote: >>> Am 04.06.2018 um 19:26 schrieb Stephan Eggermont <stephan(a)stack.nl>: >>> Ah, nice. How is that guarded against concurrent access, live-lock & >>> dead-lock? >>> >> Usually git supports that out of the box. I hope libgit does not do anything different. > > https://danluu.com/file-consistency/ > https://danluu.com/filesystem-errors/ > > And we have multiple libgit versions from the different vms accessing the > same repo that need to work on a lot of different file systems > Ok, but where is the problem? Norbert

June 5, 2018

Re: [Pharo-users] Loading Local Repositories with Iceberg

by Stephan Eggermont

Norbert Hartl <norbert(a)hartl.name> wrote: >> Am 04.06.2018 um 19:26 schrieb Stephan Eggermont <stephan(a)stack.nl>: >> Ah, nice. How is that guarded against concurrent access, live-lock & >> dead-lock? >> > Usually git supports that out of the box. I hope libgit does not do anything different. https://danluu.com/file-consistency/ https://danluu.com/filesystem-errors/ And we have multiple libgit versions from the different vms accessing the same repo that need to work on a lot of different file systems Stephan

June 5, 2018

Re: [Pharo-users] Loading Local Repositories with Iceberg

by Norbert Hartl

> Am 04.06.2018 um 15:59 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > hi, > >> On 4 Jun 2018, at 12:57, Stephan Eggermont <stephan(a)stack.nl> wrote: >> >> Evan Donahue <emdonahu(a)gmail.com> wrote: >>> I have "Share repositories between images" checked in both images, >> >> Share repositories at the moment just provides a shared location on disk >> where the repositories are located. That is only useful if you are very >> disciplined about stashing and switching to the branch needed for your >> current image, and you only have one image open at a time. > > not really. > P7 will force you to be in the right branch or you will not be able to doâ¦ almost anything :) > you can have two (or ten) images opened at once and work on them, but at a moment you will need to ârepairâ each image to commit. > How does this work if the other image has updated the git index? Repairing will update&merge, too? That is usually the reason I commit always first so I commit to a prior version of the index in order to have git merge on update. Norbert > Esteban > >> >> Stephan >> >> >> >> >> > >

June 5, 2018

Re: [Pharo-users] Loading Local Repositories with Iceberg

by Norbert Hartl

> Am 04.06.2018 um 19:26 schrieb Stephan Eggermont <stephan(a)stack.nl>: > > Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > . >> P7 will force you to be in the right branch or you will not be able to >> doâ¦ almost anything :) >> you can have two (or ten) images opened at once and work on them, but at >> a moment you will need to ârepairâ each image to commit. > > Ah, nice. How is that guarded against concurrent access, live-lock & > dead-lock? > Usually git supports that out of the box. I hope libgit does not do anything different. > Stephan > > >

June 5, 2018

need help loading third-party packages

by Gregg Williams

Hi--another question, this time on loading an external package into Pharo. I want to do some work manipulating text, so I thought I would start by reading the source code for an existing package that works on text. Here's what I did: On smalltalkhub.com, I found a package called Citezen, from team RMoD, and downloaded the .mcz file. There were many versions, so I downloaded the one with the latest timestamp. It helped that its name was Citezen-All-sd20.mcz. I've tried adding this to my current Pharo 6.1 image in two ways: 1) by dropping the .mcz file onto the window of PharoLauncher, and 2) moving the file into my computer's package-cache directory. I had roughly the same problems with both. Problem 1: There were multiple options for telling the system what do to with it: Load, Load Version, Merge version, Open version, and Extract all to.... Problem 2: Once I do that, I get to a window with buttons at the top: Browse, History, Changes, Load, Merge, Adopt, Copy, Diff. Problem 3: Once I chose one of these, I got at least a half-dozen "Can't find dependency <filename> Ignore?" messages (for example "...Citezen-Parsers-cdlm.13" and "...Citezen-Tests-sd.39"). The default button for this was "Yes", so I chose this. This started some downloading of files, a process that sometimes got "stuck" and never completed. Not knowing any better, I then launched Pharo 6.1 (Stable). I could see no indication that Citezen had been "added" to the system. Anyway, in a system browser, I searched for the string "Citezen" and found five Citezen packages: All, Model, PArsers, Rendering, and Tests. But when I selected any of them, no content appeared in the Class pane. Also searching for a class containing "Cite" found nothing. Surely, other beginners have had the same problem as me. I would appreciate pointers to any existing resources that would help me out, or whatever help you'd care to give me. TO RECAP, I want to load third-party packages and read their source code. What's the best way to do this? Many thanks!

June 5, 2018

How does Metacello check for installed packages in the image?

by HernÃ¡n Morales Durand

Hi, I have a Pharo 6.1 image with packages loaded manually (without BaselineOf or ConfigurationOf). Now if I evaluate a Metacello script which would install the package already installed in the image (for example via dependency), is there any check performed against the RPackages or similar to avoid loading it again? Cheers, HernÃ¡n

June 5, 2018