March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] one-click is dead, now we have platform specific builds

by Dennis Groves

To whom it may concern, **I have an opinion:** I for one prefer the one-click on OSX. It just fits into the environment better. **I have a bug:** However, after several days of it not working and lots, and lots of help on IRC we have discovered the reason that the one-click did not work on my Mac is because the filesystem is case sensitive. Thus the plist file specifies an incorrect binary as 'pharo' when it needs to be 'Pharo' this is true for the 3.0 branch as well. Cheers, Dennis -- [Dennis Groves](http://about.me/dennis.groves), MSc [Email me](mailto:dennis.groves@owasp.org) or [schedule a meeting](http://goo.gl/8sPIy). *This email is licensed under a [CC BY-ND 3.0](http://creativecommons.org/licenses/by-nd/3.0/deed.en_GB) license.* **Please do not send me Microsoft Office/Apple iWork documents.** Send [OpenDocument](http://fsf.org/campaigns/opendocument/) instead! Stand up for your freedom to install [free software](http://www.fsf.org/campaigns/secure-boot/statement). > The idea that some lives matter less is the root of all thatâs wrong > with the world. -- Paul Farmer

March 20, 2013

Re: [Pharo-project] one-click is dead, now we have platform specific builds

by Esteban Lorenzano

Hi Sean, yes, the procedure is still there, and it is still possible to produce one-click distributions... maybe we could produce a "portable" version (I think the portable concept captures better what a one-click is... because a one click is not a one click, you still need to double click on it :D ) Esteban On Mar 20, 2013, at 12:43 PM, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > EstebanLM wrote >> I just adapted the script for create one-click > > Have we captured the procedure for the one-click? Even though it didn't work > out for newbies, I think it has value in other contexts e.g. a personal > image that I can easily start up on any OS, perhaps to show off at > conferences ;) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/one-click-is-dead-now-we-have-platform-specific-build… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

March 20, 2013

Re: [Pharo-project] one-click is dead, now we have platform specific builds

by Tudor Girba

Great. I will give it a try. Doru On Mar 20, 2013, at 11:07 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > sure... I just adapted the script for create one-click. If you already do that for moose, is more or less the same: > > you need to clone from > > https://gitorious.org/pharo-build > > and then execute something like this: > > bash build-platform.sh -i image/Pharo -o Pharo3.0 -v 3.0 -t Pharo -p mac > > (obviously with your image and names and output names) > > Esteban > > On Mar 19, 2013, at 9:52 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Great! >> >> Is there a possibility to custom Pharo images (such as Moose) with your infrastructure? >> >> Cheers, >> Doru >> >> >> On Mar 19, 2013, at 6:29 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> tbh, one-click was just cool for mac users... windows and linux users (specially newcomers) where having bad reaction with the structure that the one-click enforces. >>> >>> The new scripts produces structures that can fit better into the platforms where they will run. >>> >>> You can check them here: http://files.pharo.org/platform/ >>> >>> of course, a lot of improvements are possible, this is just the first step :) >>> >>> Esteban >> >> -- >> www.tudorgirba.com >> >> "What we can governs what we wish." >> >> >> >> > -- www.tudorgirba.com "Things happen when they happen, not when you talk about them happening."

March 20, 2013

Re: [Pharo-project] Running tests on 2.0 and first impression

by StÃ©phane Ducasse

> Publishing diffs to the mailing list certainly works great for Squeak. > Squeak's commit rate is rather less than Pharo's, so it might be too > much... but the easiest way to find that out is just switching the > diff publishing on and seeing how people feel. Yes I thought about that too. especially since 3.0 will be again a strong release. Stef

March 20, 2013

Re: [Pharo-project] about mac/win/linux VM for 2.0?

by stephane ducasse

thanks! On Mar 20, 2013, at 10:05 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > I didn't planned it, but I can do it... it should be quite trivial :) > > Esteban > > On Mar 20, 2013, at 10:03 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Esteban >> >> do you plan to do the same that you did for Pharo30.app to Pharo20? >> So that we can have non oneclick platform specific vm for pharo2.0. >> >> Stef >> > >

March 20, 2013

Re: [Pharo-project] Running tests on 2.0 and first impression

by Frank Shearar

Hi Stef, Publishing diffs to the mailing list certainly works great for Squeak. Squeak's commit rate is rather less than Pharo's, so it might be too much... but the easiest way to find that out is just switching the diff publishing on and seeing how people feel. frank On 20 March 2013 20:40, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > Hello nicolas > > I know what you think about seeing code changes. So what can we do to improve it. > I'm in favor to send diff to the mailing-lists especially since SmalltalkHub will support the charge now. > > Stef >> >> Totally agree, but for this specific bug I think that the process can >> be improved by increased code reviews. >> The fact that a negative seconds inst var and a julianDayNumber inst >> var different from julianDayNumber message was chosen indicates that >> current implementation is a quick hack, a workaround for solving some >> problems, but clearly not a long term solution. IMO it creates as many >> problems as it solves. >> Diff has been added lately, and it is a real progress for reviewing >> code, but the effort to participate is still a bit high. More eyes, >> more reviews... >> >> The fact that bug only show up around midnight is true only for >> Europeans which have small offsets from UTC, I guess the probability >> of bug shall increase in California or Japan. >> >> Nicolas >> >>> >>> >>> >> > >

March 20, 2013

Re: [Pharo-project] about mac/win/linux VM for 2.0?

by Esteban Lorenzano

I didn't planned it, but I can do it... it should be quite trivial :) Esteban On Mar 20, 2013, at 10:03 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Esteban > > do you plan to do the same that you did for Pharo30.app to Pharo20? > So that we can have non oneclick platform specific vm for pharo2.0. > > Stef >

March 20, 2013

[Pharo-project] about mac/win/linux VM for 2.0?

by StÃ©phane Ducasse

Esteban do you plan to do the same that you did for Pharo30.app to Pharo20? So that we can have non oneclick platform specific vm for pharo2.0. Stef

March 20, 2013

Re: [Pharo-project] Running tests on 2.0 and first impression

by stephane ducasse

> My little contribution logically comes after the release mainly for > these reasons > 1) my previous attempts to catch up with 2.0 were abandonned because > deep changes were going on, a bit too much instability for too little > time > 2) the buzz convinced me to try again on a more stabilized image > > The failing tests amazed me a little because we now have CI to perform > this kind of dumb job. Yes we are really puzzled that there is such a difference between our servers and our machines. > > Last thing, continuous improvment certainly, but I'm not comfortable > with the process. > More than often it is necessary to download a fresh image which is > fine for a bot but is a barrier for me. can you tell me on the 593 updates how many forced people to download an image? 3 times? (When we got changesetSorter going mad and in deep endless loop) Then wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharo30.sh I even wrote a chapter for people that do not want to remember like me :) and you get a simple way to get the latest version in case the update does not work. > Probably because my stuff is just a blob of hacks, proof of concepts > or unfinished experiments, and I don't invest time into producing > re-installable artifacts. > It happens that I publish revisited stuff that is one or two years > old, so I don't like to throw too soon. > And I want to keep those hacks alive, not to bury them into a dead > fileOut or mcz. > My own view of continuous is closer to the smooth updates of Squeak trunk. Again reply to my question: what can you do if you have an deep endless loop in changeset that affects any code loading actions. We could not even pass a script to the image? We could remove the cs and say to everybody to drop a fileâ¦. but this costs us a lot of manual manipulation. This is why in 3.0 we put in place a staged process. Changes are only pushed once the CI run the tests (can load code first :)) so we want a smoother process but not at the price of moving. Because for 3.0 we have really cool stuff in preparation :) > I'd like to contribute more, and I hope you will retain the positive > part, because most certainly I will mainly report the things I don't > like ;) Please. We need people like you. We are doing our best and this is also often on our free time. Camillo, Ben, Marcus, Guille, Camille, me are not payed to work on Pharo :) We build it because we want to have a sexy and cool environment. > > cheers > > Nicolas > >> -- >> Sven Van Caekenberghe >> http://stfx.eu >> Smalltalk is the Red Pill >> >> >

March 20, 2013

Re: [Pharo-project] Running tests on 2.0 and first impression

by stephane ducasse

On Mar 20, 2013, at 2:34 PM, Miguel Moquillon <miguel.moquillon(a)gmail.com> wrote: > You're lucky, because in my own machine running GNU/Linux Ubuntu 12.04 the tests running in Pharo 2.0 either kills the VM or most of the time freezes the environment, depending on the weatherâ¦ this is fun because on our linux servers the tests are green. > > Miguel > > Le 20/03/2013 00:54, Nicolas Cellier a Ã©crit : >> First thing, congrats to Pharo community, I observe a good trend. >> It may seem dumb, but it's great to have pharo executable and pharo icons. >> Once the image launched, my general feel is good too, though I'm not >> fan of multiple keys shortcuts. >> It stressed me to the point that I didn't realize the single key >> shortcuts were still active in text editor (desperately seeking cmd b+ >> something... when cmd + shift + N would just browse ivar references). >> I guess I'll get used to it. >> Browsing the class Object seems a bit long, I guess there's time >> wasted scanning the class hierarchy... >> >> Of course, there's a few things to polish. >> First I ran the tests, and here is what I have to say about it >> - there were two interactions requests, IMO, there shouldn't be any (a >> pop up for my name, and a menu) >> - there are some failures (10) and errors (3), is this expected? (see >> attachment) >> - more annoyingly, during the test, the progressbar feedback >> disappeared (sporadically flashing) and the TestRunner feedback too >> (number of succeded test updates went scarce) >> >> When I opened a FileBrowser to browse the filedOut TestRunner report, >> I typed *.txt as a filter and got a RegexSyntaxError nullable closure, >> that's surprising. >> >> There I stopped exploring the features and inquired a bit about the failures. >> Most failures are related to DateAndTime. I guess they occured because >> I was playing with image around midnight with a +01:00 offset. >> Early debugging let me see some highly questionable code, using >> negative seconds in internal representation is a recipe for trouble.. >> Having julianDayNumber the instance variable being different from >> julianDayNumber the message is also asking for trouble. >> >> Well, just wanted to share this first feedback, i think i have lot of >> things to discover in this image (I guess good things, but you know >> me, I generally report the bad first). >> >> cheers >> >> Nicolas > > -- > L'Intelligence Artificielle n'a aucune chance face Ã la StupiditÃ© Naturelle > >

March 20, 2013