- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Iceberg and other repos

by Nicolas Passerini

Yes, I do not know exactly why, but Metacello will not update your packages if you do that. On Thu, Sep 22, 2016 at 12:27 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 22.09.2016 um 11:56 schrieb Nicolas Passerini <npasserini(a)gmail.com>: > > > On Thu, Sep 22, 2016 at 11:43 AM, Norbert Hartl <norbert(a)hartl.name> > wrote: > >> I'm using stable, sorry for not saying. >> > > No worries. > > I think it is fixed in the newer development version, but let me check it > and I will come back to you. > > I loaded > > Metacello new > baseline: 'Iceberg'; > repository: 'github://npasserini/iceberg:master'; > load. > > but the problem still exists. I must confess that I struggle to use this > properly. By executing the expression above I cannot see what I really > updated. Monticello browser is not of any help. I can see Iceberg.package > which is bold. Loading the package does not seem to do anything and the > package stays bold. > > Norbert > >

Sept. 22, 2016

Re: [Pharo-dev] Iceberg and other repos

by Norbert Hartl

> Am 22.09.2016 um 11:56 schrieb Nicolas Passerini <npasserini(a)gmail.com>: > > > On Thu, Sep 22, 2016 at 11:43 AM, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > I'm using stable, sorry for not saying. > > No worries. > > I think it is fixed in the newer development version, but let me check it and I will come back to you. I loaded Metacello new baseline: 'Iceberg'; repository: 'github://npasserini/iceberg:master'; load. but the problem still exists. I must confess that I struggle to use this properly. By executing the expression above I cannot see what I really updated. Monticello browser is not of any help. I can see Iceberg.package which is bold. Loading the package does not seem to do anything and the package stays bold. Norbert

Sept. 22, 2016

Re: [Pharo-dev] Iceberg and other repos

by Nicolas Passerini

On Thu, Sep 22, 2016 at 11:43 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > I'm using stable, sorry for not saying. > No worries. I think it is fixed in the newer development version, but let me check it and I will come back to you.

Sept. 22, 2016

Better diffs

by Nicolas Passerini

I am not happy with Iceberg diffs so I wonder if there is a better diff morphs around. Currently I am using a GLMDiffPresentation, which gives an easy way to show a diff, but is not much flexible. Some requirements I have are: a. Configure coloring (currently changes are always shown in red for the left version and in green for the right version). b. Provide a title for each side of the diff c. (more difficult) Show three way diffs. Also highlighting is just not right in current version, several times it does not highlight correctly the changed code. So, do you know if there is a better way to show diffs? Thank you. Nico

Sept. 22, 2016

Re: [Pharo-dev] Iceberg and other repos

by Norbert Hartl

I'm using stable, sorry for not saying. I loaded Metacello new baseline: 'Iceberg'; repository: 'github://npasserini/iceberg:stable'; load. Norbert > Am 22.09.2016 um 11:30 schrieb Nicolas Passerini <npasserini(a)gmail.com>: > > Hi Norbert, are you using the stable version or the develpment one? > > > On Thu, Sep 22, 2016 at 10:49 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > https://github.com/npasserini/iceberg/issues <https://github.com/npasserini/iceberg/issues> > > but I think this one is already reported (at least, I know I have talk with Nico about it :P) > > Esteban > > > On 22 Sep 2016, at 10:37, Norbert Hartl <norbert(a)hartl.name <mailto:norbert@hartl.name>> wrote: > > > > I loaded my project with gitfiletree and tried to use it with iceberg. But I get > > > > <Bildschirmfoto 2016-09-22 um 10.35.31.png> > > > > It seems that Iceberg assumes that packages are loaded with Iceberg itself. Meaning if the repository is not an iceberg repository #loadedVersion returns nil. > > > > So where to report bugs for iceberg? > > > > Norbert > > > > >

Sept. 22, 2016

Re: [Pharo-dev] Iceberg and other repos

by Nicolas Passerini

Hi Norbert, are you using the stable version or the develpment one? On Thu, Sep 22, 2016 at 10:49 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > https://github.com/npasserini/iceberg/issues > > but I think this one is already reported (at least, I know I have talk > with Nico about it :P) > > Esteban > > > On 22 Sep 2016, at 10:37, Norbert Hartl <norbert(a)hartl.name> wrote: > > > > I loaded my project with gitfiletree and tried to use it with iceberg. > But I get > > > > <Bildschirmfoto 2016-09-22 um 10.35.31.png> > > > > It seems that Iceberg assumes that packages are loaded with Iceberg > itself. Meaning if the repository is not an iceberg repository > #loadedVersion returns nil. > > > > So where to report bugs for iceberg? > > > > Norbert > > > > >

Sept. 22, 2016

Re: [Pharo-dev] Iceberg and other repos

by Esteban Lorenzano

https://github.com/npasserini/iceberg/issues but I think this one is already reported (at least, I know I have talk with Nico about it :P) Esteban > On 22 Sep 2016, at 10:37, Norbert Hartl <norbert(a)hartl.name> wrote: > > I loaded my project with gitfiletree and tried to use it with iceberg. But I get > > <Bildschirmfoto 2016-09-22 um 10.35.31.png> > > It seems that Iceberg assumes that packages are loaded with Iceberg itself. Meaning if the repository is not an iceberg repository #loadedVersion returns nil. > > So where to report bugs for iceberg? > > Norbert >

Sept. 22, 2016

Iceberg and other repos

by Norbert Hartl

I loaded my project with gitfiletree and tried to use it with iceberg. But I get It seems that Iceberg assumes that packages are loaded with Iceberg itself. Meaning if the repository is not an iceberg repository #loadedVersion returns nil. So where to report bugs for iceberg? Norbert

Sept. 22, 2016

Re: [Pharo-dev] ExternalSemaphoreTable curious garbageCollect

by Ben Coman

On Thu, Sep 22, 2016 at 2:54 PM, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > The semaphores are strongly held, but not the objects that put them there. > Sockets are the main users of the table. > Sockets are finalized by removing registered semaphores from the table. > Garbage collect triggers finalization. > > Hence, garbage collect can result in slots being freed. Gotcha.Thanks for that insight. Socket>>finalize self primSocketDestroyGently: socketHandle. Smalltalk unregisterExternalObject: semaphore. Smalltalk unregisterExternalObject: readSemaphore. Smalltalk unregisterExternalObject: writeSemaphore. cheers -ben

Sept. 22, 2016

Re: [Pharo-dev] ZnPortNotANumber exception when loading from local clone dir (following Metacello Guide)

by Sven Van Caekenberghe

> On 22 Sep 2016, at 00:19, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi Sven, > > thanks. Did not notice that I need three instead of two slashes. So no need > to explicitly convert to ZnUrl. > > So for the records this is what works: > > > pathToPackageDirectory := 'C:\ClonedRepo\packages'. > Metacello new > baseline: 'MyProject'; > repository: ('gitfiletree:///', pathToPackageDirectory) ; > load. So mixing back & forward slashes works ? Pretty weird ;-) > Thanks > T. > >> Gesendet: Dienstag, 20. September 2016 um 20:41 Uhr >> Von: "Sven Van Caekenberghe" <sven(a)stfx.eu> >> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Betreff: Re: [Pharo-dev] ZnPortNotANumber exception when loading from local clone dir (following Metacello Guide) >> >> Hi Torsten, >> >> Just for the ZnUrl part, have a look at >> >> ZnFileUrlTests>>#testWindowsDriveNamesInFileUrl >> >> AFAIK, your example should be written as: >> >> ('filetree:///' , 'C:/ClonedRepo/packages') asZnUrl. >> >> Or maybe, >> >> (FileLocator C / 'ClonedRepo' / 'packages') asZnUrl. >> >> Sven >> >>> On 20 Sep 2016, at 20:30, Torsten Bergmann <astares(a)gmx.de> wrote: >>> >>> Hi, >>> >>> according to the Metacello quide on [1] in section "Prime Metacello registry" one can write >>> >>> | pathToPackageDirectory | >>> "edit to match the path to your chosen package directory" >>> pathToPackageDirectory := '/opt/git/Sample/packages'. >>> Metacello new >>> baseline: 'Sample'; >>> repository: 'filetree://', pathToPackageDirectory; >>> load. >>> >>> Adopting this for a Windows path I have: >>> >>> | pathToPackageDirectory | >>> pathToPackageDirectory := 'C:\ClonedRepo\packages'. >>> Metacello new >>> baseline: 'MyProject'; >>> repository: 'filetree://', pathToPackageDirectory; >>> load. >>> >>> But I get a ZnPortNotANumber exception, even when I use a diffent protocol like "client://". >>> Tried this in Pharo 6.0 Latest update: #60233 >>> >>> What I want to do (on Windows) is to load all project packages from a local cloned git >>> directory (not a remote GitHub) using the dependencies given in the Baseline. >>> >>> Did I miss something, is it just broken or the docu not up to date? If so is this a parsing issue on the Zinc URLs >>> or an issue of Metacello API? >>> >>> Thanks >>> T. >>> >>> [1] https://github.com/dalehenrich/metacello-work/blob/master/docs/GettingStart… >>> >> >> >> >

Sept. 22, 2016