- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PharoSound load error in Pharo 2.0

by jannik.laval

On Aug 18, 2013, at 10:18 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Aug 18, 2013, at 8:42 AM, jannik.laval <jannik.laval(a)gmail.com> wrote: > >> Hum, I do not understand. >> When I load it with your script it works (it loads the version 75 of Sound). >> Now, with Phratch it tries to load the version 76 of Sound. >> >> Here is my configuration: >> >> === >> baseline10: spec >> <version:'1.0-baseline'> >> spec for: #common do: [ >> spec blessing: #baseline. >> spec repository: 'http://smalltalkhub.com/mc/JLaval/Phratch/main'. >> spec project: 'Sound' with: [ >> spec >> repository: 'http://smalltalkhub.com/mc/PharoExtras/Sound/main'; >> versionString: #stable; >> className: 'ConfigurationOfPharoSound']. >> spec package: 'Phratch' with: [ >> spec requires: 'Sound'. >> ]. >> ]. >> === >> > > did you try with '5.3'? to see Yes, I tried and I have the same behavior. There is something I do not understand, and the chapter about Metacello does not help me :( Jannik > >> And I load it with : >> (ConfigurationOfPhratch project latestVersion: #baseline) load. >> >> So, why does it not take the stable version of PharoSound ? > > > I do not know. we should ask dale. > >> >> Thanks for the help. >> Jannik >> >> >> >> On Aug 17, 2013, at 7:03 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> jannik >>> >>> >>> (ConfigurationOfPharoSound project version: '5.3') load >>> >>> loads perfectly in 2.0 >>> >>> >>> stable: spec >>> <symbolicVersion: #stable> >>> >>> spec for: #'pharo1.0.x' version: '1.0'. >>> spec for: #'pharo1.1.x' version: '3.0'. >>> spec for: #'pharo1.2.x' version: '3.0'. >>> spec for: #'pharo1.4.x' version: '5.0'. >>> spec for: #'pharo2.0.x' version: '5.3'. >>> spec for: #'pharo3.0.x' version: '5.4'. >>> >>> (ConfigurationOfPharoSound project version: '5.3') load >>> loads perfectly on a freshly downloaded 2.0 image >>> >>> So tell me more. >>> >>> Stef >>> >>> >> >> > >

Aug. 18, 2013

Re: [Pharo-dev] PharoSound load error in Pharo 2.0

by StÃ©phane Ducasse

On Aug 18, 2013, at 8:42 AM, jannik.laval <jannik.laval(a)gmail.com> wrote: > Hum, I do not understand. > When I load it with your script it works (it loads the version 75 of Sound). > Now, with Phratch it tries to load the version 76 of Sound. > > Here is my configuration: > > === > baseline10: spec > <version:'1.0-baseline'> > spec for: #common do: [ > spec blessing: #baseline. > spec repository: 'http://smalltalkhub.com/mc/JLaval/Phratch/main'. > spec project: 'Sound' with: [ > spec > repository: 'http://smalltalkhub.com/mc/PharoExtras/Sound/main'; > versionString: #stable; > className: 'ConfigurationOfPharoSound']. > spec package: 'Phratch' with: [ > spec requires: 'Sound'. > ]. > ]. > === > did you try with '5.3'? to see > And I load it with : > (ConfigurationOfPhratch project latestVersion: #baseline) load. > > So, why does it not take the stable version of PharoSound ? I do not know. we should ask dale. > > Thanks for the help. > Jannik > > > > On Aug 17, 2013, at 7:03 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> jannik >> >> >> (ConfigurationOfPharoSound project version: '5.3') load >> >> loads perfectly in 2.0 >> >> >> stable: spec >> <symbolicVersion: #stable> >> >> spec for: #'pharo1.0.x' version: '1.0'. >> spec for: #'pharo1.1.x' version: '3.0'. >> spec for: #'pharo1.2.x' version: '3.0'. >> spec for: #'pharo1.4.x' version: '5.0'. >> spec for: #'pharo2.0.x' version: '5.3'. >> spec for: #'pharo3.0.x' version: '5.4'. >> >> (ConfigurationOfPharoSound project version: '5.3') load >> loads perfectly on a freshly downloaded 2.0 image >> >> So tell me more. >> >> Stef >> >> > >

Aug. 18, 2013

Re: [Pharo-dev] I would prefer to see the diff from Smalltalkhub than Git commits

by StÃ©phane Ducasse

On Aug 17, 2013, at 9:54 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > On 2013-08-17, at 21:26, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> nope, the smalltalk hub diffs are clearly minor >>> >>> - they are auto generate, no manual intervention needed to send them >>> - they are only sent if the build succeeds >>> - they include valuable information >> like what? > > I see exactly which classes and methods were touched with little effort. I do not see the point to get a list of selectors. > Which saves me clicks on each package and then browsing through the diff on smalltalkhub. This is ok now I do not think that we should continue to send these mails to the list because there are not diff but list of selectors so they have much lower added values. I would be curious to know how many people systematically click on one link to see a change. This is why I would like to avoid to force people to put filter on their mailing-list. >>> - the github repository is the place where you go to find changes, it's simply impossible to figure out when something broke on smalltalkhub since you cannot compare multiple packages over multiple times >> >> I do not to go to github to see the diff because I will not do it and I want to see the code modified. > > because? Because this is what I want. I want to see the changes right in the mails in front of my nose. It works well in Squeak so I do not see why it would not work for Pharo. > >> It worked really well in the squeak mailing-list we did not do it because squeaksource was on its knees. >> Nicolas will fix SmalltalkHub diff and I will see how the script loader can send the diffs > > > I guess it's a matter of taste. I know that I need the git sources to properly find bugs that were introduced by some faulty version. > And usually I control each changes made to classes I maintain, which is very easy to do for me when looking at the changes mail sent from github since I see the touched methods on classes. > A full diff, like what is done for VM-maker, is a bit too much for me, especially when it comes in pure text form (compared to for instance what I see on github?) Probably true but this is another scenario. The scenario I want to see exercised is: more people look directly in the actual changes. Stef

Aug. 18, 2013

Re: [Pharo-dev] PharoSound load error in Pharo 2.0

by jannik.laval

Hum, I do not understand. When I load it with your script it works (it loads the version 75 of Sound). Now, with Phratch it tries to load the version 76 of Sound. Here is my configuration: === baseline10: spec <version:'1.0-baseline'> spec for: #common do: [ spec blessing: #baseline. spec repository: 'http://smalltalkhub.com/mc/JLaval/Phratch/main'. spec project: 'Sound' with: [ spec repository: 'http://smalltalkhub.com/mc/PharoExtras/Sound/main'; versionString: #stable; className: 'ConfigurationOfPharoSound']. spec package: 'Phratch' with: [ spec requires: 'Sound'. ]. ]. === And I load it with : (ConfigurationOfPhratch project latestVersion: #baseline) load. So, why does it not take the stable version of PharoSound ? Thanks for the help. Jannik On Aug 17, 2013, at 7:03 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > jannik > > > (ConfigurationOfPharoSound project version: '5.3') load > > loads perfectly in 2.0 > > > stable: spec > <symbolicVersion: #stable> > > spec for: #'pharo1.0.x' version: '1.0'. > spec for: #'pharo1.1.x' version: '3.0'. > spec for: #'pharo1.2.x' version: '3.0'. > spec for: #'pharo1.4.x' version: '5.0'. > spec for: #'pharo2.0.x' version: '5.3'. > spec for: #'pharo3.0.x' version: '5.4'. > > (ConfigurationOfPharoSound project version: '5.3') load > loads perfectly on a freshly downloaded 2.0 image > > So tell me more. > > Stef > >

Aug. 18, 2013

Re: [Pharo-dev] I would prefer to see the diff from Smalltalkhub than Git commits

by Camillo Bruni

On 2013-08-17, at 21:26, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> nope, the smalltalk hub diffs are clearly minor >> >> - they are auto generate, no manual intervention needed to send them >> - they are only sent if the build succeeds >> - they include valuable information > like what? I see exactly which classes and methods were touched with little effort. Which saves me clicks on each package and then browsing through the diff on smalltalkhub. >> - the github repository is the place where you go to find changes, it's simply impossible to figure out when something broke on smalltalkhub since you cannot compare multiple packages over multiple times > > I do not to go to github to see the diff because I will not do it and I want to see the code modified. because? > It worked really well in the squeak mailing-list we did not do it because squeaksource was on its knees. > Nicolas will fix SmalltalkHub diff and I will see how the script loader can send the diffs I guess it's a matter of taste. I know that I need the git sources to properly find bugs that were introduced by some faulty version. And usually I control each changes made to classes I maintain, which is very easy to do for me when looking at the changes mail sent from github since I see the touched methods on classes. A full diff, like what is done for VM-maker, is a bit too much for me, especially when it comes in pure text form (compared to for instance what I see on github?)

Aug. 17, 2013

Re: [Pharo-dev] I would prefer to see the diff from Smalltalkhub than Git commits

by StÃ©phane Ducasse

> nope, the smalltalk hub diffs are clearly minor > > - they are auto generate, no manual intervention needed to send them > - they are only sent if the build succeeds > - they include valuable information like what? > - the github repository is the place where you go to find changes, it's simply impossible to figure out when something broke on smalltalkhub since you cannot compare multiple packages over multiple times I do not to go to github to see the diff because I will not do it and I want to see the code modified. It worked really well in the squeak mailing-list we did not do it because squeaksource was on its knees. Nicolas will fix SmalltalkHub diff and I will see how the script loader can send the diffs > and... I thought we agree that I send the diff from github. I do not remember probably but now I do not see added value. > Usually the diff gets send along with the update, but since there was a strange update that didn't change any code, the export script failed, so I catch up with the export.

Aug. 17, 2013

Re: [Pharo-dev] I would prefer to see the diff from Smalltalkhub than Git commits

by Camillo Bruni

I will disable it until I caught up with the current builds. On 2013-08-17, at 15:27, Camillo Bruni <camillobruni(a)gmail.com> wrote: > nope, the smalltalk hub diffs are clearly minor > > - they are auto generate, no manual intervention needed to send them > - they are only sent if the build succeeds > - they include valuable information > - the github repository is the place where you go to find changes, it's simply impossible to figure out when something broke on smalltalkhub since you cannot compare multiple packages over multiple times > > and... I thought we agree that I send the diff from github. > Usually the diff gets send along with the update, but since there was a strange update that didn't change any code, the export script failed, so I catch up with the export. > > > On 2013-08-16, at 17:02, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi >> >> could we avoid to get the github commits. I would prefer to get diff from Smalltalkhub. >> >> Stef >

Aug. 17, 2013

Re: [Pharo-dev] I would prefer to see the diff from Smalltalkhub than Git commits

by Camillo Bruni

nope, the smalltalk hub diffs are clearly minor - they are auto generate, no manual intervention needed to send them - they are only sent if the build succeeds - they include valuable information - the github repository is the place where you go to find changes, it's simply impossible to figure out when something broke on smalltalkhub since you cannot compare multiple packages over multiple times and... I thought we agree that I send the diff from github. Usually the diff gets send along with the update, but since there was a strange update that didn't change any code, the export script failed, so I catch up with the export. On 2013-08-16, at 17:02, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > could we avoid to get the github commits. I would prefer to get diff from Smalltalkhub. > > Stef

Aug. 17, 2013

Re: [Pharo-dev] PharoSound load error in Pharo 2.0

by StÃ©phane Ducasse

jannik (ConfigurationOfPharoSound project version: '5.3') load loads perfectly in 2.0 stable: spec <symbolicVersion: #stable> spec for: #'pharo1.0.x' version: '1.0'. spec for: #'pharo1.1.x' version: '3.0'. spec for: #'pharo1.2.x' version: '3.0'. spec for: #'pharo1.4.x' version: '5.0'. spec for: #'pharo2.0.x' version: '5.3'. spec for: #'pharo3.0.x' version: '5.4'. (ConfigurationOfPharoSound project version: '5.3') load loads perfectly on a freshly downloaded 2.0 image So tell me more. Stef

Aug. 17, 2013

Re: [Pharo-dev] PharoSound load error in Pharo 2.0

by StÃ©phane Ducasse

I will check. Did you check which version is marked as stable for 2.0 > Hi, > > When loading stable version of pharo sound in Pharo 2.0 there is a missing class: SoundSystem > > === > This package depends on the following classes: > SoundSystem > You must resolve these dependencies before you will be able to load these definitions: > BaseSoundSystem > === > > Jannik

Aug. 17, 2013