May 2013 - Pharo-users - lists.pharo.org

Re: [Pharo-users] the future of squeaksource

by stephane ducasse

On May 8, 2013, at 6:11 PM, Andrei Vasile Chis <chisvasileandrei(a)gmail.com> wrote: > We can add a search based on project names. > Also I'd like to create a virtual machine and move an instance of the SqueakSource image there. > This way if in the future people will want to access any meta-information they could download the virtual machine and get a running SqueakSource. yes this is a really good idea! > > > On Wed, May 8, 2013 at 11:25 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2013/5/7 Andrei Vasile Chis <chisvasileandrei(a)gmail.com> > I don't really think so. Read-only mode is perfect, you only waste time to > relaunch squeaksource when it crashes :) > > We were thinking at something more dramatic, like killing the image and putting all the public > licensed projects on some ftp (or something similar). > > If you go such way it will be impossible to find old projects by description and wiki page contents. Squeaksource have search. > > Lately the image has become more unstable then usual. From time to time it just hangs and keeps that processor of > the server at 100% > > >

May 8, 2013

Re: [Pharo-users] the future of squeaksource

by Paul DeBruicker

Are the project descriptions and wiki entries stored in the file system or the image? On 05/08/2013 09:07 AM, Andrei Vasile Chis wrote: > We were thinking of keeping the current image alive for one or two more > months. > Then replace it with just a simple view of the file system. > > > On Wed, May 8, 2013 at 9:50 AM, stephane ducasse > <stephane.ducasse(a)free.fr <mailto:stephane.ducasse@free.fr>> wrote: > > > On May 7, 2013, at 5:19 PM, Andrei Vasile Chis > <chisvasileandrei(a)gmail.com <mailto:chisvasileandrei@gmail.com>> wrote: > > > Hi all, > > > > Given that SmalltalkHub is now stable we were considering to > discontinue SqueakSource. > > Our idea is to provide a grace period of a couple of months to > allow the current active users to migrate their projects to the new > service and then simply put squeaksource in read-only mode (simply > exposing the directory structure and allowing downloads). > > > > What do you think about it ? > > Are there any good reasons to still keep SqueakSource alive? > > Keep it alive so that we can slowly migrate. Because migrating takes > a lot of time. > > > > > > > Cheers, > > The SCG Team > > >

May 8, 2013

Re: [Pharo-users] [ANN] ConfigurationOfOpenDBXDriver in MetaRepoForPharo20

by Chris

Thanks Guille, will be interested to know how you get on with Glorp. I've had a few issues since 1.4 where Glorp's tests didn't all pass in the test runner (they did from the system browser and seemed to work everywhere in 1.3) and it only seems to be getting worse still in 2.0 as my HDTestReport application ones are just starting to have trouble too now. I assumed it was some weird timing thing and wondered if you'd come across it? I also have a couple of personal Glorp fixes if you're interested. > Hi! > > I just took some time to load and test opendbx in 2.0, with the latest > fixes to be able to load ffi. > > The configuration stable version loads cleanly in Pharo 2.0 and the > configuration is available in the configuration browser. > > I'll continue with Glorp & friends following :) > > Guille

May 8, 2013

Re: [Pharo-users] the future of squeaksource

by Andrei Vasile Chis

We can add a search based on project names. Also I'd like to create a virtual machine and move an instance of the SqueakSource image there. This way if in the future people will want to access any meta-information they could download the virtual machine and get a running SqueakSource. On Wed, May 8, 2013 at 11:25 AM, Denis Kudriashov <dionisiydk(a)gmail.com>wrote: > 2013/5/7 Andrei Vasile Chis <chisvasileandrei(a)gmail.com> > >> I don't really think so. Read-only mode is perfect, you only waste time to >>> relaunch squeaksource when it crashes :) >>> >> >> We were thinking at something more dramatic, like killing the image and >> putting all the public >> licensed projects on some ftp (or something similar). >> > > If you go such way it will be impossible to find old projects by > description and wiki page contents. Squeaksource have search. > > >> Lately the image has become more unstable then usual. From time to time >> it just hangs and keeps that processor of >> the server at 100% >> >> > >

May 8, 2013

Re: [Pharo-users] the future of squeaksource

by Andrei Vasile Chis

Thanks. I will add this script to the front page of SqueakSource. On Wed, May 8, 2013 at 5:55 PM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > On Wed, May 8, 2013 at 4:05 PM, Hilaire Fernandes > <hilaire.fernandes(a)gmail.com> wrote: > > A small note or link in Squeaksource how to migrate to smaltalkhub will > > be helpful. > > > I agree. Something like that would make sense for people who want to > get an exact copy of their project: > > | source goSource destination goDestination files destinationFiles | > > source := MCHttpRepository location: ' > http://www.squeaksource.com/YOURPROJECT'. > destination := MCSmalltalkhubRepository owner: 'YOURNAME' project: > 'YOURPROJECT' user: 'YOURNAME' password: 'YOURPASSWORD'. > > goSource := Gofer new repository: source. > goDestination := Gofer new repository: destination. > > files := source allVersionNames. > > (goSource allResolved select: [ :resolved | files anySatisfy: [ :each > | resolved name = each ] ]) do: [ :each | goSource package: each > packageName ]. > > goSource fetch. "downloads all mcz on your computer" > > destinationFiles := destination allVersionNames. "checks what files > are already at destination" > files reject: [ :file | destinationFiles includes: file ] thenDo: [ > :file | goDestination version: file ]. "selects only the mcz that are > not yet at destination" > > goDestination push. "sends everything to SmalltalkHub" > > self assert: destination allVersionNames sorted = files sorted. > "checks we have exactly the same files at source and destination" > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

May 8, 2013

Re: [Pharo-users] the future of squeaksource

by Andrei Vasile Chis

We were thinking of keeping the current image alive for one or two more months. Then replace it with just a simple view of the file system. On Wed, May 8, 2013 at 9:50 AM, stephane ducasse <stephane.ducasse(a)free.fr>wrote: > > On May 7, 2013, at 5:19 PM, Andrei Vasile Chis <chisvasileandrei(a)gmail.com> > wrote: > > > Hi all, > > > > Given that SmalltalkHub is now stable we were considering to discontinue > SqueakSource. > > Our idea is to provide a grace period of a couple of months to allow the > current active users to migrate their projects to the new service and then > simply put squeaksource in read-only mode (simply exposing the directory > structure and allowing downloads). > > > > What do you think about it ? > > Are there any good reasons to still keep SqueakSource alive? > > Keep it alive so that we can slowly migrate. Because migrating takes a lot > of time. > > > > > > > Cheers, > > The SCG Team > > >

May 8, 2013

Re: [Pharo-users] the future of squeaksource

by Damien Cassou

On Wed, May 8, 2013 at 4:05 PM, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: > A small note or link in Squeaksource how to migrate to smaltalkhub will > be helpful. I agree. Something like that would make sense for people who want to get an exact copy of their project: | source goSource destination goDestination files destinationFiles | source := MCHttpRepository location: 'http://www.squeaksource.com/YOURPROJECT'. destination := MCSmalltalkhubRepository owner: 'YOURNAME' project: 'YOURPROJECT' user: 'YOURNAME' password: 'YOURPASSWORD'. goSource := Gofer new repository: source. goDestination := Gofer new repository: destination. files := source allVersionNames. (goSource allResolved select: [ :resolved | files anySatisfy: [ :each | resolved name = each ] ]) do: [ :each | goSource package: each packageName ]. goSource fetch. "downloads all mcz on your computer" destinationFiles := destination allVersionNames. "checks what files are already at destination" files reject: [ :file | destinationFiles includes: file ] thenDo: [ :file | goDestination version: file ]. "selects only the mcz that are not yet at destination" goDestination push. "sends everything to SmalltalkHub" self assert: destination allVersionNames sorted = files sorted. "checks we have exactly the same files at source and destination" -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

May 8, 2013

Re: [Pharo-users] the future of squeaksource

by Hilaire Fernandes

A small note or link in Squeaksource how to migrate to smaltalkhub will be helpful. Thanks Hilaire Le 07/05/2013 17:19, Andrei Vasile Chis a Ã©crit : > Hi all, > > Given that SmalltalkHub is now stable we were considering to discontinue > SqueakSource. > Our idea is to provide a grace period of a couple of months to allow the > current active users to migrate their projects to the new service and > then simply put squeaksource in read-only mode (simply exposing the > directory structure and allowing downloads). > > What do you think about it ? > Are there any good reasons to still keep SqueakSource alive? > > Cheers, > The SCG Team -- Dr. Geo http://drgeo.eu

May 8, 2013

Re: [Pharo-users] the future of squeaksource

by Denis Kudriashov

2013/5/7 Andrei Vasile Chis <chisvasileandrei(a)gmail.com> > I don't really think so. Read-only mode is perfect, you only waste time to >> relaunch squeaksource when it crashes :) >> > > We were thinking at something more dramatic, like killing the image and > putting all the public > licensed projects on some ftp (or something similar). > If you go such way it will be impossible to find old projects by description and wiki page contents. Squeaksource have search. > Lately the image has become more unstable then usual. From time to time > it just hangs and keeps that processor of > the server at 100% > >

May 8, 2013

Re: [Pharo-users] the future of squeaksource

by stephane ducasse

On May 7, 2013, at 9:15 PM, Andrei Vasile Chis <chisvasileandrei(a)gmail.com> wrote: > I don't really think so. Read-only mode is perfect, you only waste time to > relaunch squeaksource when it crashes :) > > We were thinking at something more dramatic, like killing the image and putting all the public > licensed projects on some ftp (or something similar). Yes on a ftp would be really good. Stef > Lately the image has become more unstable then usual. From time to time it just hangs and keeps that processor of > the server at 100% >

May 8, 2013