June 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] can you check the last update

by Norbert Hartl

On Wed, 2008-06-25 at 12:52 +0200, Damien Cassou wrote: > On Wed, Jun 25, 2008 at 11:05 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > On Wed, 2008-06-25 at 10:55 +0200, Damien Cassou wrote: > >> > On Wed, Jun 25, 2008 at 10:50 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> >> - removed unnecessary columns Difficulty and Priority from Issue > >> > >> Should I remove them completely from the issue tracking system? > >> > >> Fixed = Developer made requested changes, QA should verify > >> Verified = QA has verified that the fix worked > >> Invalid = This was not a valid issue report > >> Duplicate = This report duplicates an existing issue > >> WontFix = We decided to not take action on this issue > >> Closed = The fix has been treated and issue is closed > >> > > > > I don't understan. I removed the columns in the view as > > they are only disturbing. What do you mean by showing the > > list of statusses? > > I meant: > > Type-Defect = Report of a software defect > Type-Enhancement = Request for enhancement > Type-Task = Work item that doesn't change the code or docs > Type-Patch = Source code patch for review > Type-Other = Some other kind of issue > Priority-High = Strongly want to resolve in the specified milestone > Priority-Medium = Normal priority > Priority-Low = Might slip to later milestone > Difficulty-VeryEasy = Anybody can fix that in a few seconds > Difficulty-Easy = Only little knowledge and time required > Difficulty-Medium = Knowledge and time required > Difficulty-Hard = Requires more than one expert > Why you want to remove them? Now they are only visible in the admin area where to don't disturb anyone. But do as you think is best. Norbert

June 25, 2008

Re: [Pharo-project] can you check the last update

by Damien Cassou

On Wed, Jun 25, 2008 at 11:05 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > On Wed, 2008-06-25 at 10:55 +0200, Damien Cassou wrote: >> > On Wed, Jun 25, 2008 at 10:50 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> - removed unnecessary columns Difficulty and Priority from Issue >> >> Should I remove them completely from the issue tracking system? >> >> Fixed = Developer made requested changes, QA should verify >> Verified = QA has verified that the fix worked >> Invalid = This was not a valid issue report >> Duplicate = This report duplicates an existing issue >> WontFix = We decided to not take action on this issue >> Closed = The fix has been treated and issue is closed >> > > I don't understan. I removed the columns in the view as > they are only disturbing. What do you mean by showing the > list of statusses? I meant: Type-Defect = Report of a software defect Type-Enhancement = Request for enhancement Type-Task = Work item that doesn't change the code or docs Type-Patch = Source code patch for review Type-Other = Some other kind of issue Priority-High = Strongly want to resolve in the specified milestone Priority-Medium = Normal priority Priority-Low = Might slip to later milestone Difficulty-VeryEasy = Anybody can fix that in a few seconds Difficulty-Easy = Only little knowledge and time required Difficulty-Medium = Knowledge and time required Difficulty-Hard = Requires more than one expert -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 25, 2008

Re: [Pharo-project] can you check the last update

by Norbert Hartl

On Wed, 2008-06-25 at 10:55 +0200, Damien Cassou wrote: > > On Wed, Jun 25, 2008 at 10:50 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> - removed unnecessary columns Difficulty and Priority from Issue > > Should I remove them completely from the issue tracking system? > > Fixed = Developer made requested changes, QA should verify > Verified = QA has verified that the fix worked > Invalid = This was not a valid issue report > Duplicate = This report duplicates an existing issue > WontFix = We decided to not take action on this issue > Closed = The fix has been treated and issue is closed > I don't understan. I removed the columns in the view as they are only disturbing. What do you mean by showing the list of statusses? Norbert

June 25, 2008

Re: [Pharo-project] can you check the last update

by Norbert Hartl

On Wed, 2008-06-25 at 10:54 +0200, Damien Cassou wrote: > On Wed, Jun 25, 2008 at 10:50 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Ok, I changed a few things: > > > > - removed unnecessary columns Difficulty and Priority from Issue > > list view > > - added status closed so it either goes > > -> defect -> fix -> verified -> close > > or > > -> patch -> fix -> verified -> close > > - treated a few issues to have correct status > > You may want to remove other statuses. Here is the list: > > New = Issue has not had initial review yet > Accepted = Problem reproduced / Need acknowledged > Started = Work on this issue has begun > Comment = A question has been asked > > Fixed = Developer made requested changes, QA should verify > Verified = QA has verified that the fix worked > Invalid = This was not a valid issue report > Duplicate = This report duplicates an existing issue > WontFix = We decided to not take action on this issue > Closed = The fix has been treated and issue is closed Which you would delete? They are all good and useful in my opinion. The only one which isn't useful to me is "Started". Norbert

June 25, 2008

Re: [Pharo-project] can you check the last update

by Damien Cassou

> On Wed, Jun 25, 2008 at 10:50 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >> - removed unnecessary columns Difficulty and Priority from Issue Should I remove them completely from the issue tracking system? Fixed = Developer made requested changes, QA should verify Verified = QA has verified that the fix worked Invalid = This was not a valid issue report Duplicate = This report duplicates an existing issue WontFix = We decided to not take action on this issue Closed = The fix has been treated and issue is closed -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 25, 2008

Re: [Pharo-project] can you check the last update

by Damien Cassou

On Wed, Jun 25, 2008 at 10:50 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > Ok, I changed a few things: > > - removed unnecessary columns Difficulty and Priority from Issue > list view > - added status closed so it either goes > -> defect -> fix -> verified -> close > or > -> patch -> fix -> verified -> close > - treated a few issues to have correct status You may want to remove other statuses. Here is the list: New = Issue has not had initial review yet Accepted = Problem reproduced / Need acknowledged Started = Work on this issue has begun Comment = A question has been asked Fixed = Developer made requested changes, QA should verify Verified = QA has verified that the fix worked Invalid = This was not a valid issue report Duplicate = This report duplicates an existing issue WontFix = We decided to not take action on this issue Closed = The fix has been treated and issue is closed -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 25, 2008

Re: [Pharo-project] can you check the last update

by Damien Cassou

On Wed, Jun 25, 2008 at 10:26 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Maybe the best solution is to use the issue tracker on google. >> That's the purpose it serves. If someone has an update he can >> open a ticket with type "patch" and status "Fixed". If another >> one has reviewed it he can change the status to "verified". To >> see what is ready for update you just filter the issues by >> status "Verified" > > Yes we should do that http://code.google.com/p/pharo/issues/detail?id=16 -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 25, 2008

Re: [Pharo-project] can you check the last update

by Norbert Hartl

On Wed, 2008-06-25 at 10:26 +0200, StÃ©phane Ducasse wrote: > > > > We could do a SLICE for every fix so you could see what needs > > to be updated. But then it is hard to be sure someone reviewed > > it. > > > > Maybe the best solution is to use the issue tracker on google. > > That's the purpose it serves. If someone has an update he can > > open a ticket with type "patch" and status "Fixed". If another > > one has reviewed it he can change the status to "verified". To > > see what is ready for update you just filter the issues by > > status "Verified" > > Yes we should do that > Ok, I changed a few things: - removed unnecessary columns Difficulty and Priority from Issue list view - added status closed so it either goes -> defect -> fix -> verified -> close or -> patch -> fix -> verified -> close - treated a few issues to have correct status So Stef, all you have to do is to save this link http://code.google.com/p/pharo/issues/list?q=status%3AVerified&can=1 and click it if you want to know what to do ;) I hope you like it. Norbert > > > > > > Norbert > >> Stef > >> > >> On Jun 25, 2008, at 9:45 AM, Norbert Hartl wrote: > >> > >>> Are you going to harvest the rest of the packages, too? > >>> > >>> KernelTests-al.67 > >>> Monticello-al.319 > >>> > >>> are fixing all but 2 remaining tests. > >>> Norbert > >>> > >>> On Wed, 2008-06-25 at 09:00 +0200, StÃ©phane Ducasse wrote: > >>>> this is strange when I do a merge with SLICE-randomRemoval I get an > >>>> emtpy list. > >>>> Were SLICE-UnimplementedCallsFix1-NorbertHartl.1 and randomRemoval > >>>> the > >>>> same? > >>>> Should I close SLICE-randomRemoval? > >>> > >>>> Stef > >>>> > >>>> On Jun 25, 2008, at 8:52 AM, StÃ©phane Ducasse wrote: > >>>> > >>>>> Hi all > >>>>> > >>>>> I got some funny unpublished packages and I'm a bit confused. So > >>>>> could you check what I did. > >>>>> I was harvesting MVC removal + norbert cleaning SLICE- > >>>>> UnimplementedCallsFix1-NorbertHartl.1 > >>>>> > >>>>> I have to find some time (argh) to improve the process and the > >>>>> tools. because this is far too much manual. > >>>>> > >>>>> Stef > >>>>> > >>>>> _______________________________________________ > >>>>> 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 > > > > > > _______________________________________________ > > 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 25, 2008

Re: [Pharo-project] can you check the last update

by StÃ©phane Ducasse

> > We could do a SLICE for every fix so you could see what needs > to be updated. But then it is hard to be sure someone reviewed > it. > > Maybe the best solution is to use the issue tracker on google. > That's the purpose it serves. If someone has an update he can > open a ticket with type "patch" and status "Fixed". If another > one has reviewed it he can change the status to "verified". To > see what is ready for update you just filter the issues by > status "Verified" Yes we should do that > > > Norbert >> Stef >> >> On Jun 25, 2008, at 9:45 AM, Norbert Hartl wrote: >> >>> Are you going to harvest the rest of the packages, too? >>> >>> KernelTests-al.67 >>> Monticello-al.319 >>> >>> are fixing all but 2 remaining tests. >>> Norbert >>> >>> On Wed, 2008-06-25 at 09:00 +0200, StÃ©phane Ducasse wrote: >>>> this is strange when I do a merge with SLICE-randomRemoval I get an >>>> emtpy list. >>>> Were SLICE-UnimplementedCallsFix1-NorbertHartl.1 and randomRemoval >>>> the >>>> same? >>>> Should I close SLICE-randomRemoval? >>> >>>> Stef >>>> >>>> On Jun 25, 2008, at 8:52 AM, StÃ©phane Ducasse wrote: >>>> >>>>> Hi all >>>>> >>>>> I got some funny unpublished packages and I'm a bit confused. So >>>>> could you check what I did. >>>>> I was harvesting MVC removal + norbert cleaning SLICE- >>>>> UnimplementedCallsFix1-NorbertHartl.1 >>>>> >>>>> I have to find some time (argh) to improve the process and the >>>>> tools. because this is far too much manual. >>>>> >>>>> Stef >>>>> >>>>> _______________________________________________ >>>>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 25, 2008

Re: [Pharo-project] can you check the last update

by Norbert Hartl

On Wed, 2008-06-25 at 10:13 +0200, StÃ©phane Ducasse wrote: > yes this is strange :) > but ok I will move on. > Can you just check that I did not lose anything. > I checked already and it looks good for me. Norbert > stef > > On Jun 25, 2008, at 9:58 AM, Norbert Hartl wrote: > > > On Wed, 2008-06-25 at 09:44 +0200, StÃ©phane Ducasse wrote: > >> But norbert when I do an update + a merge of Slice-randomRemoval I > >> get > >> an empty list. > >> > > Yes that's true for an 10045 image as you integrated exactly that > > fix. Loading updates shows something like "..NorbertCleaning.." > > and checking the package dependencies of SLICE-RandomRemoval all > > are loaded in 10045. So I can't tell why that happened but it did. > > So you can just delete SLICE-RandomRemoval and dependencies. > > > > Norbert > > > >> Stef > >> > >> > >> On Jun 25, 2008, at 9:32 AM, Norbert Hartl wrote: > >> > >>> On Wed, 2008-06-25 at 09:00 +0200, StÃ©phane Ducasse wrote: > >>>> this is strange when I do a merge with SLICE-randomRemoval I get an > >>>> emtpy list. > >>>> Were SLICE-UnimplementedCallsFix1-NorbertHartl.1 and randomRemoval > >>>> the > >>>> same? > >>>> Should I close SLICE-randomRemoval? > >>>> > >>> No, RandomCleanup is broken and can be deleted. That was the upload > >>> problem. I renamed that to RandomRemoval to be sure that everything > >>> is fine. UnimplementedCalls is completely different and in the > >>> upstream now (in 10044). If I take a 10044 image and merge on > >>> RandomRemoval I can see the removals I've done. > >>> > >>> Norbert > >>> > >>> > >>>> Stef > >>>> > >>>> On Jun 25, 2008, at 8:52 AM, StÃ©phane Ducasse wrote: > >>>> > >>>>> Hi all > >>>>> > >>>>> I got some funny unpublished packages and I'm a bit confused. So > >>>>> could you check what I did. > >>>>> I was harvesting MVC removal + norbert cleaning SLICE- > >>>>> UnimplementedCallsFix1-NorbertHartl.1 > >>>>> > >>>>> I have to find some time (argh) to improve the process and the > >>>>> tools. because this is far too much manual. > >>>>> > >>>>> Stef > >>>>> > >>>>> _______________________________________________ > >>>>> 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 > > > > > > _______________________________________________ > > 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 25, 2008

Re: [Pharo-project] can you check the last update

by Norbert Hartl

On Wed, 2008-06-25 at 09:54 +0200, StÃ©phane Ducasse wrote: > yes > I'm just losing time because sometimes there is not enough information > for me. > So may be we should have a wiki so that I can follow what I should > integrate. > As this is the inbox everything should be treated until it is empty. I thought this was the reason for TreatedInbox. We could do a SLICE for every fix so you could see what needs to be updated. But then it is hard to be sure someone reviewed it. Maybe the best solution is to use the issue tracker on google. That's the purpose it serves. If someone has an update he can open a ticket with type "patch" and status "Fixed". If another one has reviewed it he can change the status to "verified". To see what is ready for update you just filter the issues by status "Verified" Norbert > Stef > > On Jun 25, 2008, at 9:45 AM, Norbert Hartl wrote: > > > Are you going to harvest the rest of the packages, too? > > > > KernelTests-al.67 > > Monticello-al.319 > > > > are fixing all but 2 remaining tests. > > Norbert > > > > On Wed, 2008-06-25 at 09:00 +0200, StÃ©phane Ducasse wrote: > >> this is strange when I do a merge with SLICE-randomRemoval I get an > >> emtpy list. > >> Were SLICE-UnimplementedCallsFix1-NorbertHartl.1 and randomRemoval > >> the > >> same? > >> Should I close SLICE-randomRemoval? > > > >> Stef > >> > >> On Jun 25, 2008, at 8:52 AM, StÃ©phane Ducasse wrote: > >> > >>> Hi all > >>> > >>> I got some funny unpublished packages and I'm a bit confused. So > >>> could you check what I did. > >>> I was harvesting MVC removal + norbert cleaning SLICE- > >>> UnimplementedCallsFix1-NorbertHartl.1 > >>> > >>> I have to find some time (argh) to improve the process and the > >>> tools. because this is far too much manual. > >>> > >>> Stef > >>> > >>> _______________________________________________ > >>> 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 25, 2008

Re: [Pharo-project] can you check the last update

by StÃ©phane Ducasse

yes this is strange :) but ok I will move on. Can you just check that I did not lose anything. stef On Jun 25, 2008, at 9:58 AM, Norbert Hartl wrote: > On Wed, 2008-06-25 at 09:44 +0200, StÃ©phane Ducasse wrote: >> But norbert when I do an update + a merge of Slice-randomRemoval I >> get >> an empty list. >> > Yes that's true for an 10045 image as you integrated exactly that > fix. Loading updates shows something like "..NorbertCleaning.." > and checking the package dependencies of SLICE-RandomRemoval all > are loaded in 10045. So I can't tell why that happened but it did. > So you can just delete SLICE-RandomRemoval and dependencies. > > Norbert > >> Stef >> >> >> On Jun 25, 2008, at 9:32 AM, Norbert Hartl wrote: >> >>> On Wed, 2008-06-25 at 09:00 +0200, StÃ©phane Ducasse wrote: >>>> this is strange when I do a merge with SLICE-randomRemoval I get an >>>> emtpy list. >>>> Were SLICE-UnimplementedCallsFix1-NorbertHartl.1 and randomRemoval >>>> the >>>> same? >>>> Should I close SLICE-randomRemoval? >>>> >>> No, RandomCleanup is broken and can be deleted. That was the upload >>> problem. I renamed that to RandomRemoval to be sure that everything >>> is fine. UnimplementedCalls is completely different and in the >>> upstream now (in 10044). If I take a 10044 image and merge on >>> RandomRemoval I can see the removals I've done. >>> >>> Norbert >>> >>> >>>> Stef >>>> >>>> On Jun 25, 2008, at 8:52 AM, StÃ©phane Ducasse wrote: >>>> >>>>> Hi all >>>>> >>>>> I got some funny unpublished packages and I'm a bit confused. So >>>>> could you check what I did. >>>>> I was harvesting MVC removal + norbert cleaning SLICE- >>>>> UnimplementedCallsFix1-NorbertHartl.1 >>>>> >>>>> I have to find some time (argh) to improve the process and the >>>>> tools. because this is far too much manual. >>>>> >>>>> Stef >>>>> >>>>> _______________________________________________ >>>>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 25, 2008

Re: [Pharo-project] can you check the last update

by Norbert Hartl

On Wed, 2008-06-25 at 09:44 +0200, StÃ©phane Ducasse wrote: > But norbert when I do an update + a merge of Slice-randomRemoval I get > an empty list. > Yes that's true for an 10045 image as you integrated exactly that fix. Loading updates shows something like "..NorbertCleaning.." and checking the package dependencies of SLICE-RandomRemoval all are loaded in 10045. So I can't tell why that happened but it did. So you can just delete SLICE-RandomRemoval and dependencies. Norbert > Stef > > > On Jun 25, 2008, at 9:32 AM, Norbert Hartl wrote: > > > On Wed, 2008-06-25 at 09:00 +0200, StÃ©phane Ducasse wrote: > >> this is strange when I do a merge with SLICE-randomRemoval I get an > >> emtpy list. > >> Were SLICE-UnimplementedCallsFix1-NorbertHartl.1 and randomRemoval > >> the > >> same? > >> Should I close SLICE-randomRemoval? > >> > > No, RandomCleanup is broken and can be deleted. That was the upload > > problem. I renamed that to RandomRemoval to be sure that everything > > is fine. UnimplementedCalls is completely different and in the > > upstream now (in 10044). If I take a 10044 image and merge on > > RandomRemoval I can see the removals I've done. > > > > Norbert > > > > > >> Stef > >> > >> On Jun 25, 2008, at 8:52 AM, StÃ©phane Ducasse wrote: > >> > >>> Hi all > >>> > >>> I got some funny unpublished packages and I'm a bit confused. So > >>> could you check what I did. > >>> I was harvesting MVC removal + norbert cleaning SLICE- > >>> UnimplementedCallsFix1-NorbertHartl.1 > >>> > >>> I have to find some time (argh) to improve the process and the > >>> tools. because this is far too much manual. > >>> > >>> Stef > >>> > >>> _______________________________________________ > >>> 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 25, 2008

Re: [Pharo-project] can you check the last update

by StÃ©phane Ducasse

yes I'm just losing time because sometimes there is not enough information for me. So may be we should have a wiki so that I can follow what I should integrate. Stef On Jun 25, 2008, at 9:45 AM, Norbert Hartl wrote: > Are you going to harvest the rest of the packages, too? > > KernelTests-al.67 > Monticello-al.319 > > are fixing all but 2 remaining tests. > Norbert > > On Wed, 2008-06-25 at 09:00 +0200, StÃ©phane Ducasse wrote: >> this is strange when I do a merge with SLICE-randomRemoval I get an >> emtpy list. >> Were SLICE-UnimplementedCallsFix1-NorbertHartl.1 and randomRemoval >> the >> same? >> Should I close SLICE-randomRemoval? > >> Stef >> >> On Jun 25, 2008, at 8:52 AM, StÃ©phane Ducasse wrote: >> >>> Hi all >>> >>> I got some funny unpublished packages and I'm a bit confused. So >>> could you check what I did. >>> I was harvesting MVC removal + norbert cleaning SLICE- >>> UnimplementedCallsFix1-NorbertHartl.1 >>> >>> I have to find some time (argh) to improve the process and the >>> tools. because this is far too much manual. >>> >>> Stef >>> >>> _______________________________________________ >>> 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 25, 2008

Re: [Pharo-project] can you check the last update

by Norbert Hartl

Are you going to harvest the rest of the packages, too? KernelTests-al.67 Monticello-al.319 are fixing all but 2 remaining tests. Norbert On Wed, 2008-06-25 at 09:00 +0200, StÃ©phane Ducasse wrote: > this is strange when I do a merge with SLICE-randomRemoval I get an > emtpy list. > Were SLICE-UnimplementedCallsFix1-NorbertHartl.1 and randomRemoval the > same? > Should I close SLICE-randomRemoval? > Stef > > On Jun 25, 2008, at 8:52 AM, StÃ©phane Ducasse wrote: > > > Hi all > > > > I got some funny unpublished packages and I'm a bit confused. So > > could you check what I did. > > I was harvesting MVC removal + norbert cleaning SLICE- > > UnimplementedCallsFix1-NorbertHartl.1 > > > > I have to find some time (argh) to improve the process and the > > tools. because this is far too much manual. > > > > Stef > > > > _______________________________________________ > > 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 25, 2008

Re: [Pharo-project] can you check the last update

by StÃ©phane Ducasse

But norbert when I do an update + a merge of Slice-randomRemoval I get an empty list. Stef On Jun 25, 2008, at 9:32 AM, Norbert Hartl wrote: > On Wed, 2008-06-25 at 09:00 +0200, StÃ©phane Ducasse wrote: >> this is strange when I do a merge with SLICE-randomRemoval I get an >> emtpy list. >> Were SLICE-UnimplementedCallsFix1-NorbertHartl.1 and randomRemoval >> the >> same? >> Should I close SLICE-randomRemoval? >> > No, RandomCleanup is broken and can be deleted. That was the upload > problem. I renamed that to RandomRemoval to be sure that everything > is fine. UnimplementedCalls is completely different and in the > upstream now (in 10044). If I take a 10044 image and merge on > RandomRemoval I can see the removals I've done. > > Norbert > > >> Stef >> >> On Jun 25, 2008, at 8:52 AM, StÃ©phane Ducasse wrote: >> >>> Hi all >>> >>> I got some funny unpublished packages and I'm a bit confused. So >>> could you check what I did. >>> I was harvesting MVC removal + norbert cleaning SLICE- >>> UnimplementedCallsFix1-NorbertHartl.1 >>> >>> I have to find some time (argh) to improve the process and the >>> tools. because this is far too much manual. >>> >>> Stef >>> >>> _______________________________________________ >>> 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 25, 2008

Re: [Pharo-project] can you check the last update

by StÃ©phane Ducasse

Thanks I deleted RandomCleanup And will proceed the other one as time let me do it. Stef On Jun 25, 2008, at 9:32 AM, Norbert Hartl wrote: > On Wed, 2008-06-25 at 09:00 +0200, StÃ©phane Ducasse wrote: >> this is strange when I do a merge with SLICE-randomRemoval I get an >> emtpy list. >> Were SLICE-UnimplementedCallsFix1-NorbertHartl.1 and randomRemoval >> the >> same? >> Should I close SLICE-randomRemoval? >> > No, RandomCleanup is broken and can be deleted. That was the upload > problem. I renamed that to RandomRemoval to be sure that everything > is fine. UnimplementedCalls is completely different and in the > upstream now (in 10044). If I take a 10044 image and merge on > RandomRemoval I can see the removals I've done. > > Norbert > > >> Stef >> >> On Jun 25, 2008, at 8:52 AM, StÃ©phane Ducasse wrote: >> >>> Hi all >>> >>> I got some funny unpublished packages and I'm a bit confused. So >>> could you check what I did. >>> I was harvesting MVC removal + norbert cleaning SLICE- >>> UnimplementedCallsFix1-NorbertHartl.1 >>> >>> I have to find some time (argh) to improve the process and the >>> tools. because this is far too much manual. >>> >>> Stef >>> >>> _______________________________________________ >>> 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 25, 2008

Re: [Pharo-project] can you check the last update

by Norbert Hartl

On Wed, 2008-06-25 at 09:00 +0200, StÃ©phane Ducasse wrote: > this is strange when I do a merge with SLICE-randomRemoval I get an > emtpy list. > Were SLICE-UnimplementedCallsFix1-NorbertHartl.1 and randomRemoval the > same? > Should I close SLICE-randomRemoval? > No, RandomCleanup is broken and can be deleted. That was the upload problem. I renamed that to RandomRemoval to be sure that everything is fine. UnimplementedCalls is completely different and in the upstream now (in 10044). If I take a 10044 image and merge on RandomRemoval I can see the removals I've done. Norbert > Stef > > On Jun 25, 2008, at 8:52 AM, StÃ©phane Ducasse wrote: > > > Hi all > > > > I got some funny unpublished packages and I'm a bit confused. So > > could you check what I did. > > I was harvesting MVC removal + norbert cleaning SLICE- > > UnimplementedCallsFix1-NorbertHartl.1 > > > > I have to find some time (argh) to improve the process and the > > tools. because this is far too much manual. > > > > Stef > > > > _______________________________________________ > > 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 25, 2008

[Pharo-project] milestone 1

by StÃ©phane Ducasse

for milestone 1 - it would be good to have a Pharo in the flap (if any flap) and any other better looking lesssqueakish look :L) if one of you has time :) - when do we want to finish. It would be good to have milestone 1 out for esug or before. - I would really like to see the items of 3.10 examined. for milestone 2 - better building process - something that I would like us to do is to have a task force writing some good class comments. If you can think about that it would be good. Purpose of the class Main methods Main collaborators Example Internal representation Stef

June 25, 2008

Re: [Pharo-project] can you check the last update

by StÃ©phane Ducasse

this is strange when I do a merge with SLICE-randomRemoval I get an emtpy list. Were SLICE-UnimplementedCallsFix1-NorbertHartl.1 and randomRemoval the same? Should I close SLICE-randomRemoval? Stef On Jun 25, 2008, at 8:52 AM, StÃ©phane Ducasse wrote: > Hi all > > I got some funny unpublished packages and I'm a bit confused. So > could you check what I did. > I was harvesting MVC removal + norbert cleaning SLICE- > UnimplementedCallsFix1-NorbertHartl.1 > > I have to find some time (argh) to improve the process and the > tools. because this is far too much manual. > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 25, 2008

[Pharo-project] can you check the last update

by StÃ©phane Ducasse

Hi all I got some funny unpublished packages and I'm a bit confused. So could you check what I did. I was harvesting MVC removal + norbert cleaning SLICE- UnimplementedCallsFix1-NorbertHartl.1 I have to find some time (argh) to improve the process and the tools. because this is far too much manual. Stef

June 25, 2008

[Pharo-project] harvested SLICE-UnimplementedCallsFix1-NorbertHartl.1.mcz

by StÃ©phane Ducasse

hi all I merged the SLICE-UnimplementedCallsFix1-NorbertHartl.1.mcz Please have a look because sometimes I'm tired and I can press load instead of merge. I will harvest the other items. Stef

June 24, 2008

Re: [Pharo-project] Sapphire at Smalltalk Solutions Reno ;-)

by StÃ©phane Ducasse

:) I'm sure not but we will let people judge in 6 to 8 months. For now we should focus on the 0.1 release. > > ...hope Pharo is less of a gamble ;-) > > Michael

June 24, 2008

[Pharo-project] Sapphire at Smalltalk Solutions Reno ;-)

by Michael Rueger

...hope Pharo is less of a gamble ;-) Michael

June 24, 2008

Re: [Pharo-project] random cleanups

by StÃ©phane Ducasse

I will harvest them. I was really busy over the week-end Stef On Jun 23, 2008, at 9:52 AM, Adrian Lienhard wrote: > Thanks, now SLICE-RandomRemoval works for me. > Adrian > > On Jun 22, 2008, at 16:18 , Norbert Hartl wrote: > >> On Sun, 2008-06-22 at 15:45 +0200, Adrian Lienhard wrote: >>> On Jun 22, 2008, at 15:36 , Norbert Hartl wrote: >>> >>>> 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. >>> >>> It does not work... It probably works for you because you have those >>> packages in your local cache. Can you try what I suggested above? I >>> think it will work like this. >>> >> That is strange as I used I complete fresh directory without any >> package >> cache to load it back. >> >> Anyway I did all changes again created a new SLICE-RandomRemoval and >> uploaded that together. >> >> Norbert >> >>> Adrian >>> >>> >>>> >>>> >>>> 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 >>>> >>>> >>>> _______________________________________________ >>>> 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 24, 2008

Re: [Pharo-project] bundles identification?

by StÃ©phane Ducasse

yes but we could also idnetify packages that are only used as config map. Stef On Jun 23, 2008, at 8:37 AM, Damien Cassou wrote: > On Sun, Jun 22, 2008 at 5:25 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Hi >> >> do you see a simple way to know if a package is used as a >> configuration map >> ie >> pier-all, moose-all >> >> because I would like to avoid to be forced to attach metadata to >> any package >> and in case of bundles I would like to be able to attach meta-data >> to only >> these. > > I don't think so because we use Monticello with its dependency > mechanism and I believe a package can be a dependency of multiple > other packages. > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 23, 2008

Re: [Pharo-project] random cleanups

by Adrian Lienhard

Thanks, now SLICE-RandomRemoval works for me. Adrian On Jun 22, 2008, at 16:18 , Norbert Hartl wrote: > On Sun, 2008-06-22 at 15:45 +0200, Adrian Lienhard wrote: >> On Jun 22, 2008, at 15:36 , Norbert Hartl wrote: >> >>> 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. >> >> It does not work... It probably works for you because you have those >> packages in your local cache. Can you try what I suggested above? I >> think it will work like this. >> > That is strange as I used I complete fresh directory without any > package > cache to load it back. > > Anyway I did all changes again created a new SLICE-RandomRemoval and > uploaded that together. > > Norbert > >> Adrian >> >> >>> >>> >>> 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 >>> >>> >>> _______________________________________________ >>> 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 23, 2008

Re: [Pharo-project] bundles identification?

by Damien Cassou

On Sun, Jun 22, 2008 at 5:25 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > do you see a simple way to know if a package is used as a configuration map > ie > pier-all, moose-all > > because I would like to avoid to be forced to attach metadata to any package > and in case of bundles I would like to be able to attach meta-data to only > these. I don't think so because we use Monticello with its dependency mechanism and I believe a package can be a dependency of multiple other packages. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 23, 2008

[Pharo-project] bundles identification?

by StÃ©phane Ducasse

Hi do you see a simple way to know if a package is used as a configuration map ie pier-all, moose-all because I would like to avoid to be forced to attach metadata to any package and in case of bundles I would like to be able to attach meta-data to only these. Sytef

June 22, 2008

Re: [Pharo-project] random cleanups

by StÃ©phane Ducasse

I will harvest that as soon as I have a moment. Certainly later today. Stef On Jun 22, 2008, at 4:18 PM, Norbert Hartl wrote: > On Sun, 2008-06-22 at 15:45 +0200, Adrian Lienhard wrote: >> On Jun 22, 2008, at 15:36 , Norbert Hartl wrote: >> >>> 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. >> >> It does not work... It probably works for you because you have those >> packages in your local cache. Can you try what I suggested above? I >> think it will work like this. >> > That is strange as I used I complete fresh directory without any > package > cache to load it back. > > Anyway I did all changes again created a new SLICE-RandomRemoval and > uploaded that together. > > Norbert > >> Adrian >> >> >>> >>> >>> 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 >>> >>> >>> _______________________________________________ >>> 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] test run

by Norbert Hartl

On Sun, 2008-06-22 at 15:51 +0200, Adrian Lienhard wrote: > On Jun 22, 2008, at 15:45 , Norbert Hartl wrote: > > > On Sun, 2008-06-22 at 12:42 +0200, 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) > >> > > Hmmm I'm not sure if it is a good idea to delete this test. It is > > a kind of test like ReleaseTest>>testUndeclared. It isn't critical > > but it helps moving to a clean target. I would opt to keep the test. > > At least I would turn it into a "expected failure" as long as we > > aren't far enough to state this to be totally clean. > > I'm fine with making this test an expected failure if we want to make > it pass in the future (in this case the test should exclude some cases > where it is ok that there are no implementors, like for tests that > compile those methods at runtime). Hmm, I wasn't sure myself if a test case is the right place to check. Maybe those tests are better suitable in a class where they can be exectued. Norbert

June 22, 2008

Re: [Pharo-project] random cleanups

by Norbert Hartl

On Sun, 2008-06-22 at 15:45 +0200, Adrian Lienhard wrote: > On Jun 22, 2008, at 15:36 , Norbert Hartl wrote: > > > 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. > > It does not work... It probably works for you because you have those > packages in your local cache. Can you try what I suggested above? I > think it will work like this. > That is strange as I used I complete fresh directory without any package cache to load it back. Anyway I did all changes again created a new SLICE-RandomRemoval and uploaded that together. Norbert > Adrian > > > > > > > > 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 > > > > > > _______________________________________________ > > 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] test run

by Adrian Lienhard

On Jun 22, 2008, at 15:45 , Norbert Hartl wrote: > On Sun, 2008-06-22 at 12:42 +0200, 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) >> > Hmmm I'm not sure if it is a good idea to delete this test. It is > a kind of test like ReleaseTest>>testUndeclared. It isn't critical > but it helps moving to a clean target. I would opt to keep the test. > At least I would turn it into a "expected failure" as long as we > aren't far enough to state this to be totally clean. I'm fine with making this test an expected failure if we want to make it pass in the future (in this case the test should exclude some cases where it is ok that there are no implementors, like for tests that compile those methods at runtime). Adrian

June 22, 2008

Re: [Pharo-project] Re: Missing PluggableTextController andPluggableTextView

by Damien Cassou

On Fri, Jun 20, 2008 at 8:49 PM, Andrew Tween <amtween(a)hotmail.com> wrote: > Hi Alain & Damien, > Thanks to both of you. > > I have merged in the changes... > > http://source.wiresong.ca/ob/OB-Morphic-tween.48.mcz > > http://www.squeaksource.com/shout/Shout.3.15-tween.72.mcz > > Damien, please could you update the Universe Shout entry like you did > before? Thanks. Done. Thank you for the fixes. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 22, 2008

Re: [Pharo-project] test run

by Norbert Hartl

On Sun, 2008-06-22 at 15:07 +0200, StÃ©phane Ducasse wrote: > Ok I was not aware that alain published packages in the inbox. I will > go over them. > Did norbert published his packages finally? > Yes, the necessary ones weren't problematic. Only the RandomCleanup one which is not essential. Norbert > 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 > > > > > _______________________________________________ > 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 Norbert Hartl

On Sun, 2008-06-22 at 12:42 +0200, 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) > Hmmm I'm not sure if it is a good idea to delete this test. It is a kind of test like ReleaseTest>>testUndeclared. It isn't critical but it helps moving to a clean target. I would opt to keep the test. At least I would turn it into a "expected failure" as long as we aren't far enough to state this to be totally clean. > So now, using the other fixes of Norbert, the only test failing is > #testUnwindDebuggerWithStep > I wrote an email to squeak-dev and got response from Andreas. I'll try to dig into it und come up with a solution. Great what you did anyway. Now we are on the (how is "Zielgerade" called in english ?? :) ) Norbert > 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] random cleanups

by Adrian Lienhard

On Jun 22, 2008, at 15:36 , Norbert Hartl wrote: > 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. It does not work... It probably works for you because you have those packages in your local cache. Can you try what I suggested above? I think it will work like this. Adrian > > > 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 > > > _______________________________________________ > 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] 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

Re: [Pharo-project] slive mvc removeal 3

by StÃ©phane Ducasse

I just converted it and push a new update Stef On Jun 20, 2008, at 5:45 PM, StÃ©phane Ducasse wrote: > I did not checked but indeed you removed already a lot of MCV core > classes :) > So the next step is to do the same for etoy :) > > > On Jun 20, 2008, at 9:51 AM, Alain Plantec wrote: > >> On Friday 20 June 2008 09:34:49 StÃ©phane Ducasse wrote: >>> so after we should remove the MVC classes? >> Which classes do you have in mind ? >> Have I missed something about mvc? let me know and I will >> investigate. >> alain >>> >>> Stef >>> >>> On Jun 19, 2008, at 4:56 PM, Alain Plantec wrote: >>> >>>> Hi all, >>>> I've posted it to PharoInbox: >>>> - it removes more mvc stuff >>>> - it cleans SreenController and SMPackage by the emoving of all mvc >>>> related methods (especially old mvc screen menus) >>>> I don't see anything else to do for mvc. If someone have an idea, >>>> let me known... >>>> alain >>>> <mvc-removing- >>>> step3.2.cs.zip>_______________________________________________ >>>> 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 21, 2008

Re: [Pharo-project] random cleanups

by Adrian Lienhard

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. 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

June 21, 2008

Re: [Pharo-project] random cleanups

by StÃ©phane Ducasse

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 >

June 21, 2008