- Pharo-dev - lists.pharo.org

Re: [Pharo-project] random cleanups

by Norbert Hartl

On Sat, 2008-06-21 at 16:03 +0200, Adrian Lienhard wrote: > The package is in the inbox but as it turns out, the slice refers to a > version with another UUID (the file name does not matter for resolving > the dependency). Maybe this is because you committed again with the > same name, so it could be that the original problem was a different one. > > Norbert, I suggest you take a fresh image, load the 5 packages from > the inbox and then create a new slice package and commit that too. > I took my old image and saved the slice once more. I tested to loead with a fresh image and it works now. Norbert > HTH, > Adrian > > > On Jun 21, 2008, at 13:43 , StÃ©phane Ducasse wrote: > > > Norbert may be the package is in your local cache but failed to be > > uploaded. > > > > Stef > > > > On Jun 21, 2008, at 10:12 AM, Norbert Hartl wrote: > > > >> On Sat, 2008-06-21 at 09:28 +0200, Alexandre Bergel wrote: > >>> Hi Norbert, > >>> > >>> I tried to load your slice, but I got "can't find dependency > >>> MorphicExtras-NorbertHartl.38" > >>> > >>> How such a situation may occur? > >>> > >> I don't know. I didn't get an error while uploading. I saved > >> the package again with the same name. > >> > >> Norbert > >>> Cheers, > >>> Alexandre > >>> > >>> On 20 Jun 2008, at 22:54, Norbert Hartl wrote: > >>> > >>>> I browsed a little bit through the image and found > >>>> odd things. I deleted them in > >>>> > >>>> SLICE-RandomCleanup > >>>> > >>>> I think all of them a pretty harmless changes. > >>>> > >>>> Norbert > >>>> > >>>> > >>>> _______________________________________________ > >>>> Pharo-project mailing list > >>>> Pharo-project(a)lists.gforge.inria.fr > >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>>> > >>> > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 22, 2008

Re: [Pharo-project] For milestone 2

by StÃ©phane Ducasse

On Jun 22, 2008, at 2:11 PM, Lukas Renggli wrote: >> I do not get your last sentence. What kind of integration? > > Most prominent, Monticello dispatches through PackageInfo to find out > what parts of the system belong to that package. Earlier versions of > Seaside used this mechanism to have overlapping packages (e.g. for > specific platforms). Ok but I think that this part should be change in the future to get first class package. > Furthermore PackageInfo defines a mechanism to > define pre-load, post-load, pre-unload and post-unload scripts. So I will hook into packageInfo. This should be one line change for what I have done (nothing exciting for now). > > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 22, 2008

Re: [Pharo-project] test run

by StÃ©phane Ducasse

Ok I was not aware that alain published packages in the inbox. I will go over them. Did norbert published his packages finally? Stef On Jun 22, 2008, at 12:42 PM, Adrian Lienhard wrote: > I made 3 more tests pass: > > - Fixed Monticello to pass MCSnapshotBrowserTest>>testButtonMutex > (Monticello-al.317) > - Fix FloatTest to not depend on platform for representation of NaN > bit pattern (KernelTests-al.67) > - Remove test testUnimplementedNonPrimitiveCalls (Tests-al.25) > > So now, using the other fixes of Norbert, the only test failing is > #testUnwindDebuggerWithStep > > Cheers, > Adrian > > PS: Stef, it seems that the package versions from the last update > you made are still in PharoInbox. > > On Jun 20, 2008, at 23:11 , Norbert Hartl wrote: > >> I applied all changes from the inbox and the test >> run showed expected results, 2 expected, 4 failures. >> >> Norbert >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 22, 2008

Re: [Pharo-project] For milestone 2

by Lukas Renggli

> I do not get your last sentence. What kind of integration? Most prominent, Monticello dispatches through PackageInfo to find out what parts of the system belong to that package. Earlier versions of Seaside used this mechanism to have overlapping packages (e.g. for specific platforms). Furthermore PackageInfo defines a mechanism to define pre-load, post-load, pre-unload and post-unload scripts. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

June 22, 2008

Re: [Pharo-project] test run

by Adrian Lienhard

I made 3 more tests pass: - Fixed Monticello to pass MCSnapshotBrowserTest>>testButtonMutex (Monticello-al.317) - Fix FloatTest to not depend on platform for representation of NaN bit pattern (KernelTests-al.67) - Remove test testUnimplementedNonPrimitiveCalls (Tests-al.25) So now, using the other fixes of Norbert, the only test failing is #testUnwindDebuggerWithStep Cheers, Adrian PS: Stef, it seems that the package versions from the last update you made are still in PharoInbox. On Jun 20, 2008, at 23:11 , Norbert Hartl wrote: > I applied all changes from the inbox and the test > run showed expected results, 2 expected, 4 failures. > > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 22, 2008

Re: [Pharo-project] For milestone 2

by StÃ©phane Ducasse

Just a stupid little project I started to be able to add metadata (diagram, text,.... to packages). On Jun 22, 2008, at 11:17 AM, Adrian Lienhard wrote: > What is "DrDoc"? > Adrian > > On Jun 22, 2008, at 09:27 , StÃ©phane Ducasse wrote: > >> Hi guys >> >> I would like to get DrDoc to document each package or bundle of >> packages. >> As part of the documentation I would also like to include SmallLint >> rules that have to hold. >> If you have any idea how we can support the creation of better >> package with meta data >> please let me know. >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 22, 2008

Re: [Pharo-project] For milestone 2

by StÃ©phane Ducasse

Yes I was planning to migrate my solution so that the class I generate is a subclass of PackageInfo. On Jun 22, 2008, at 9:43 AM, Lukas Renggli wrote: >> I would like to get DrDoc to document each package or bundle of >> packages. >> As part of the documentation I would also like to include SmallLint >> rules >> that have to hold. >> If you have any idea how we can support the creation of better >> package with >> meta data >> please let me know. > > PackageInfo was designed so that it can be subclassed within packages > to define additional meta-data. Currently only very few packages use > this feature. The advantage of the existing mechanism is that > Monticello already integrates with PackageInfo. I do not get your last sentence. What kind of integration? > > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 22, 2008

Re: [Pharo-project] For milestone 2

by Adrian Lienhard

What is "DrDoc"? Adrian On Jun 22, 2008, at 09:27 , StÃ©phane Ducasse wrote: > Hi guys > > I would like to get DrDoc to document each package or bundle of > packages. > As part of the documentation I would also like to include SmallLint > rules that have to hold. > If you have any idea how we can support the creation of better > package with meta data > please let me know. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 22, 2008

Re: [Pharo-project] For milestone 2

by Lukas Renggli

> I would like to get DrDoc to document each package or bundle of packages. > As part of the documentation I would also like to include SmallLint rules > that have to hold. > If you have any idea how we can support the creation of better package with > meta data > please let me know. PackageInfo was designed so that it can be subclassed within packages to define additional meta-data. Currently only very few packages use this feature. The advantage of the existing mechanism is that Monticello already integrates with PackageInfo. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

June 22, 2008

[Pharo-project] For milestone 2

by StÃ©phane Ducasse

Hi guys I would like to get DrDoc to document each package or bundle of packages. As part of the documentation I would also like to include SmallLint rules that have to hold. If you have any idea how we can support the creation of better package with meta data please let me know.

June 22, 2008