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

Re: [Pharo-project] About a system to build image

by Norbert Hartl

On Wed, 2008-07-02 at 12:26 +0200, StÃ©phane Ducasse wrote: > >> > > No, but I use Installer for my stuff. I take an official > > image, file in patches and Installer. > > do you have a script for that? > Yes, I have a handful of scripts but they are rather not very interesting. It's not that magic. If have a repository of all used packages on disk. Then I file in a static version of Installer.st. Then I use Installer to upgrade itself from the repository. After that I have e.g. whooka := Installer monticello directory: ( FileDirectory on: '/opt/whooka/repository/' ). whooka install: 'DynamicBindings-gc.7'. That should use a universe package which then installs the package and its dependents. Multiple entries allow you to install any combination of packages even if they are not combined in the universe that way. Additional information about where to get the test and which to run could be use- ful. You can put information about what to test somewhere and a mechanism creates a file like the snippet above. The files could be numbered so it could act like a queue. I don't think you need much more than that. The hard part is IMHO if a debugger is opened somewhere due an error misconfiguration. Then everything will go stale. I hope there is an easy way to prevent that and make the test fail. The last resort would be to timeout a test and kill the image, marking the test failed. > > On top of that I load > > all packages with Installer and save the image. The configuration > > and the tests are provided as a startup script to the image. > > That works all quite well. > > could you should us a typical script > I use it to configure seaside (Session class, Root class and database credentials). In the simplest case it would just invoke the test runner and lets all tests run. It doesn't even have to be an extra script. It could be the last lines in the above script. Norbert > > I would like to see that we use a universe to feed a build > > server. Then we have another reason to maintain a universe :) > > and we could enhance universe to include information about > > the combinations that work. > > Yes this would be good. > We will have a look at Sake. > > > > > > > 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

July 2, 2008

Re: [Pharo-project] About a system to build image

by Damien Cassou

On Wed, Jul 2, 2008 at 11:58 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I would really like that we start to think about a build server. > ie a system that starts with an image and a package list and run > the test. > > Here is a list of paths > - using Installer > - using Sake (I have to have a look at it). > - DevImageCreator Currently, DevImageCreator is a bash script which uses Installer and its Universe back-end. I've already dialoged with Keith about Sake and its use for dev-images. I will let you know. -- 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)

July 2, 2008

Re: [Pharo-project] Bug tracker (was 3dot10 fixes)

by StÃ©phane Ducasse

exactly. I think that you can learn from code google and having a good tracker may be using magritte would be good. Stef On Jul 2, 2008, at 12:30 PM, Janko MivÅ¡ek wrote: > Ok guys, understandable. Also let the SPM evolve a bit more to the > point that you won't hesitate a minute to switch to it :) > > > Janko > > StÃ©phane Ducasse wrote: >> + 1 >>>>>> >>>>> SPM is still in development but with more usage I'm sure Nicolas >>>>> will speed up work. But comparing with Google Code, we are near >>>>> already, IMHO. What do you think? >>>> >>>> I think we should not change again now. We already migrated from http://pharo.gforge.inria.fr/ >>>> to Google code and it works fairly well. I think we should >>>> reconsider this decision at a later point. >>>> >>> +1 >>> >>> Changing again would be pure pain :) And the tool doesn't really >>> matter if you get it done. It's the people using it. > > > -- > Janko MivÅ¡ek > AIDA/Web > Smalltalk Web Application Server > http://www.aidaweb.si > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 2, 2008

Re: [Pharo-project] Bug tracker (was 3dot10 fixes)

by Janko MivÅ¡ek

Ok guys, understandable. Also let the SPM evolve a bit more to the point that you won't hesitate a minute to switch to it :) Janko StÃ©phane Ducasse wrote: > + 1 > >>>>> >>>> SPM is still in development but with more usage I'm sure Nicolas >>>> will speed up work. But comparing with Google Code, we are near >>>> already, IMHO. What do you think? >>> >>> I think we should not change again now. We already migrated from >>> http://pharo.gforge.inria.fr/ >>> to Google code and it works fairly well. I think we should >>> reconsider this decision at a later point. >>> >> +1 >> >> Changing again would be pure pain :) And the tool doesn't really >> matter if you get it done. It's the people using it. -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

July 2, 2008

Re: [Pharo-project] About a system to build image

by StÃ©phane Ducasse

>> > No, but I use Installer for my stuff. I take an official > image, file in patches and Installer. do you have a script for that? > On top of that I load > all packages with Installer and save the image. The configuration > and the tests are provided as a startup script to the image. > That works all quite well. could you should us a typical script > I would like to see that we use a universe to feed a build > server. Then we have another reason to maintain a universe :) > and we could enhance universe to include information about > the combinations that work. Yes this would be good. We will have a look at Sake. > > > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 2, 2008

Re: [Pharo-project] About a system to build image

by Norbert Hartl

On Wed, 2008-07-02 at 11:58 +0200, StÃ©phane Ducasse wrote: > Hi all, > > I would really like that we start to think about a build server. > ie a system that starts with an image and a package list and run > the test. > > Here is a list of paths > - using Installer > - using Sake (I have to have a look at it). > - DevImageCreator > > Do you have other pointers? > No, but I use Installer for my stuff. I take an official image, file in patches and Installer. On top of that I load all packages with Installer and save the image. The configuration and the tests are provided as a startup script to the image. That works all quite well. I would like to see that we use a universe to feed a build server. Then we have another reason to maintain a universe :) and we could enhance universe to include information about the combinations that work. Norbert

July 2, 2008

Re: [Pharo-project] 3dot10 issues

by StÃ©phane Ducasse

Excellent this is cool to see this list. Stef On Jul 2, 2008, at 10:43 AM, Norbert Hartl wrote: > I have created issues for all of the fixes mentioned on > > http://code.google.com/p/pharo/wiki/ThreeDotTenFixes > > After that I scanned the numbering (I chose the summary to include > the number at beginning for sorting) and closed to gaps. The gaps > have type comment and appear on the open issues list. I didn't take > the time to scan mantis for the mantis number which includes the > fix. We can arrange that. > > All issues have "Type-Squeak" being source of a squeak version fix > and "Fixed" as a status. My proposal is that everyone takes tickets > produces slices from it and changes the status to verified after > uploading. > > To see all issues have a look at: > > http://code.google.com/p/pharo/issues/list?can=1&q=type:Squeak&sort=summary… > > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 2, 2008

Re: [Pharo-project] Bug tracker (was 3dot10 fixes)

by StÃ©phane Ducasse

+ 1 >>>> >>> SPM is still in development but with more usage I'm sure Nicolas >>> will speed up work. But comparing with Google Code, we are near >>> already, IMHO. What do you think? >> >> I think we should not change again now. We already migrated from http://pharo.gforge.inria.fr/ >> to Google code and it works fairly well. I think we should >> reconsider this decision at a later point. >> > +1 > > Changing again would be pure pain :) And the tool doesn't really > matter if you get it done. It's the people using it.

July 2, 2008

[Pharo-project] About a system to build image

by StÃ©phane Ducasse

Hi all, I would really like that we start to think about a build server. ie a system that starts with an image and a package list and run the test. Here is a list of paths - using Installer - using Sake (I have to have a look at it). - DevImageCreator Do you have other pointers? Stef

July 2, 2008

Re: [Pharo-project] 3dot10 issues

by StÃ©phane Ducasse

Normally all the code published on mantis is MIT. Stef > I have created issues for all of the fixes mentioned on > > http://code.google.com/p/pharo/wiki/ThreeDotTenFixes > > After that I scanned the numbering (I chose the summary to include > the number at beginning for sorting) and closed to gaps. The gaps > have type comment and appear on the open issues list. I didn't take > the time to scan mantis for the mantis number which includes the > fix. We can arrange that. > > All issues have "Type-Squeak" being source of a squeak version fix > and "Fixed" as a status. My proposal is that everyone takes tickets > produces slices from it and changes the status to verified after > uploading. > > To see all issues have a look at: > > http://code.google.com/p/pharo/issues/list?can=1&q=type:Squeak&sort=summary… > > Norbert

July 2, 2008