April 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Monticello: Script to suck up versions from a filetree repository and copy them to an HTTP repository?

by Peter Uhnak

On Fri, Apr 28, 2017 at 01:05:47AM +0800, Ben Coman wrote: > The natural thing for us in pharo-land is to script to movement of MC HTTP > repos to git. > This article describes why it actually could be worthwhile ensuring moving > git to MC HTTP is also easy... Technically speaking moving between GitFileTree and MC should be bi-directional, at least in the old script there was nothing requiring the endpoint be git (it is just deep copy of commits between two MC repos). Now I am updating the script, and I don't know if it will be preserved, but I'll keep it in mind. Peter > > https://www.joelonsoftware.com/2000/06/03/strategy-letter-iii-let-me-go-bac… > > cheers -ben > > On Fri, Apr 28, 2017 at 12:35 AM, Thierry Goubier <thierry.goubier(a)gmail.com > > wrote: > > > Hi Eliot, > > > > this is not possible in a FileTree repository, since it requires > > manipulating the underlying vcs, which may be anything. > > > > If it is a git-based repository used with filetree, then there are other > > solutions: gitfiletree and iceberg will show you the list of versions and > > allow you to access all of them. A Gofer script may then be used to export > > the versions one by one to any repository, if you really require that. > > > > Regards, > > > > Thierry > > > > > > Le 27/04/2017 Ã 18:24, Eliot Miranda a Ã©crit : > > > >> Hi All, > >> > >> anyone have a script for copying versions of packages in filetree > >> repositories into MC HTTP repositories? > >> > >> I'm looking at a filetree: repository for a package right now and... > >> - in the repository browser only Foo.package appears, not a list of > >> versions > >> - when I view the history of the package I get a list of versions but > >> there is no menu on selections from the list, so no obvious way of > >> accessing a version (browsing it, copying it, viewing differences > >> between versions, etc) > >> > >> _,,,^..^,,,_ > >> best, Eliot > >> > > > > > >

April 27, 2017

Re: [Pharo-dev] IMPORTANT: iceberg home changed

by Esteban Lorenzano

> On 27 Apr 2017, at 18:01, phil(a)highoctane.be wrote: > > Cool. > > I see "Whenever you decide to push your commits, Iceberg will require your github credentials. Currently Iceberg (in its default configuration) can not use SSH keys to connect to github, so you will have to provide your github user and password." > > Is there a workaround? I am using (and am required to use) ssh keys to access several git repos I deal with. > thatâs outdated (as the pictures, etc.) :P you can use ssh and in theory you can also use https (then you will be asked to provide your credentials) Esteban > Phil > > On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > As part of our work for release, I changed the home of Iceberg into his own place: https://github.com/pharo-vcs/iceberg <https://github.com/pharo-vcs/iceberg> > > So, now to install you will need: > > Metacello new > baseline: 'Iceberg'; > repository: 'github://pharo-vcs/iceberg:dev-0.4'; > load. > > I also uploaded a Configuration to the *catalog>http://catalog.pharo.org <http://catalog.pharo.org/>*, so you can load while > doing the transition. >

April 27, 2017

Re: [Pharo-dev] Monticello: Script to suck up versions from a filetree repository and copy them to an HTTP repository?

by Ben Coman

The natural thing for us in pharo-land is to script to movement of MC HTTP repos to git. This article describes why it actually could be worthwhile ensuring moving git to MC HTTP is also easy... https://www.joelonsoftware.com/2000/06/03/strategy-letter-iii-let-me-go-bac… cheers -ben On Fri, Apr 28, 2017 at 12:35 AM, Thierry Goubier <thierry.goubier(a)gmail.com > wrote: > Hi Eliot, > > this is not possible in a FileTree repository, since it requires > manipulating the underlying vcs, which may be anything. > > If it is a git-based repository used with filetree, then there are other > solutions: gitfiletree and iceberg will show you the list of versions and > allow you to access all of them. A Gofer script may then be used to export > the versions one by one to any repository, if you really require that. > > Regards, > > Thierry > > > Le 27/04/2017 Ã 18:24, Eliot Miranda a Ã©crit : > >> Hi All, >> >> anyone have a script for copying versions of packages in filetree >> repositories into MC HTTP repositories? >> >> I'm looking at a filetree: repository for a package right now and... >> - in the repository browser only Foo.package appears, not a list of >> versions >> - when I view the history of the package I get a list of versions but >> there is no menu on selections from the list, so no obvious way of >> accessing a version (browsing it, copying it, viewing differences >> between versions, etc) >> >> _,,,^..^,,,_ >> best, Eliot >> > > >

April 27, 2017

Re: [Pharo-dev] Monticello: Script to suck up versions from a filetree repository and copy them to an HTTP repository?

by Thierry Goubier

Hi Eliot, this is not possible in a FileTree repository, since it requires manipulating the underlying vcs, which may be anything. If it is a git-based repository used with filetree, then there are other solutions: gitfiletree and iceberg will show you the list of versions and allow you to access all of them. A Gofer script may then be used to export the versions one by one to any repository, if you really require that. Regards, Thierry Le 27/04/2017 Ã 18:24, Eliot Miranda a Ã©crit : > Hi All, > > anyone have a script for copying versions of packages in filetree > repositories into MC HTTP repositories? > > I'm looking at a filetree: repository for a package right now and... > - in the repository browser only Foo.package appears, not a list of versions > - when I view the history of the package I get a list of versions but > there is no menu on selections from the list, so no obvious way of > accessing a version (browsing it, copying it, viewing differences > between versions, etc) > > _,,,^..^,,,_ > best, Eliot

April 27, 2017

Re: [Pharo-dev] Meanwhile in FogBugz: issue 20000

by Sven Van Caekenberghe

> On 27 Apr 2017, at 17:49, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi, > > our community today hit the 20000 issues mark in FogBugz. > > https://pharo.fogbugz.com/f/cases/20000 > > And a good change to once again say THANK YOU, especially to the ones who care most on > > - updating the bug tracker > - fixing issues > - reviewing issues > - integrating issues > - doing also the boring tasks in caring about the bugtracker > - pushing Pharo in the right direction > > Just wow and impressive! Pharo 6 will be another nice milestone in a lively open source > Smalltalk system that we all wanted to see becoming a reality! +100 > Thx > T. > > BTW: > The issue 20000 is about clickable URLs in Help Browser. Currently we copy them to clipboard - as we do > not have web browser support in the default image. I guess it is too late to push this package into the > image due to the freeze. > > So this slices nonetheless tries to improve the situation by checking if the unified WebBrowser support package > (which is available since a year [1]) is loaded or not. If it is loaded it opens a real web browser. > > So when Pharo 6 is released and someone may lament about not being able for the URLs to really work > we can point him to load the "WebBrowser" package and he should be fine. > > [1] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2016-April/12072… >

April 27, 2017

Monticello: Script to suck up versions from a filetree repository and copy them to an HTTP repository?

by Eliot Miranda

Hi All, anyone have a script for copying versions of packages in filetree repositories into MC HTTP repositories? I'm looking at a filetree: repository for a package right now and... - in the repository browser only Foo.package appears, not a list of versions - when I view the history of the package I get a list of versions but there is no menu on selections from the list, so no obvious way of accessing a version (browsing it, copying it, viewing differences between versions, etc) _,,,^..^,,,_ best, Eliot

April 27, 2017

Re: [Pharo-dev] IMPORTANT: iceberg home changed

by phil＠highoctane.be

Cool. I see "Whenever you decide to push your commits, Iceberg will require your github credentials. Currently Iceberg (in its default configuration) can not use SSH keys to connect to github, so you will have to provide your github user and password." Is there a workaround? I am using (and am required to use) ssh keys to access several git repos I deal with. Phil On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > As part of our work for release, I changed the home of Iceberg into his > own place: https://github.com/pharo-vcs/iceberg > > So, now to install you will need: > > Metacello new > baseline: 'Iceberg'; > repository: 'github://pharo-vcs/iceberg:dev-0.4'; > load. > > I also uploaded a Configuration to the *catalog>http://catalog.pharo.org*, > so you can load while > doing the transition. >

April 27, 2017

IMPORTANT: iceberg home changed

by Esteban Lorenzano

As part of our work for release, I changed the home of Iceberg into his own place: https://github.com/pharo-vcs/iceberg So, now to install you will need: Metacello new baseline: 'Iceberg'; repository: 'github://pharo-vcs/iceberg:dev-0.4'; load. I also uploaded a Configuration to the *catalog>http://catalog.pharo.org*, so you can load while doing the transition.

April 27, 2017

Meanwhile in FogBugz: issue 20000

by Torsten Bergmann

Hi, our community today hit the 20000 issues mark in FogBugz. https://pharo.fogbugz.com/f/cases/20000 And a good change to once again say THANK YOU, especially to the ones who care most on - updating the bug tracker - fixing issues - reviewing issues - integrating issues - doing also the boring tasks in caring about the bugtracker - pushing Pharo in the right direction Just wow and impressive! Pharo 6 will be another nice milestone in a lively open source Smalltalk system that we all wanted to see becoming a reality! Thx T. BTW: The issue 20000 is about clickable URLs in Help Browser. Currently we copy them to clipboard - as we do not have web browser support in the default image. I guess it is too late to push this package into the image due to the freeze. So this slices nonetheless tries to improve the situation by checking if the unified WebBrowser support package (which is available since a year [1]) is loaded or not. If it is loaded it opens a real web browser. So when Pharo 6 is released and someone may lament about not being able for the URLs to really work we can point him to load the "WebBrowser" package and he should be fine. [1] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2016-April/12072…

April 27, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60473 Home: https://github.com/pharo-project/pharo-core

April 27, 2017