IMPORTANT: iceberg home changed
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.
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@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.
On 27 Apr 2017, at 18:01, phil@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@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.
EstebanLM wrote
Currently Iceberg (in its default configuration) can not use SSH keys to connect to github
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)
Awesome! I use SSH keys exclusively so that is great news :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/IMPORTANT-iceberg-home-changed-tp4944480p4944642.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
esteban do we have a naming convention on github? pharo-xxx? Stef On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <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
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.
Hi, not really, but we want to promote pharo related stuff with the pharo prefix on the organisations (and those who in someway will fall under our umbrella).. pharo-project -> core pharo pharo-vcs -> iceberg, libgit2 bindings, in the future: an iceberg page, maybe other backends. pharo-graphics -> block/brick and upcoming graphical cool stuff pharo-gtools -> gtools + glamour, etc. pharo-nosql -> voyage family pharo-? -> I donât know, whatever in the future, with the upcoming versions of iceberg + bootstrap, projects like iceberg, gtools, etc. will be âsubtreesâ of pharo-core so is good to have them well organised. of course people are free to name their projects/organisation as they want, but I was trying to figure out a way for *us* :) (and since is very easy to change, we could just reorganise everything under pharo-project if we decide to put everything in just one repository). Esteban
On 28 Apr 2017, at 10:11, Stephane Ducasse <stepharo.self@gmail.com> wrote:
esteban do we have a naming convention on github? pharo-xxx?
Stef
On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <estebanlm@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.
Why not make a Pharo team , we already have one for the books which also has a weird name "square bracker associates" , we should make a pharo team and put all the repos there so people can find them in one place On Fri, Apr 28, 2017 at 11:31 AM Esteban Lorenzano <estebanlm@gmail.com> wrote:
Hi,
not really, but we want to promote pharo related stuff with the pharo prefix on the organisations (and those who in someway will fall under our umbrella)..
pharo-project -> core pharo pharo-vcs -> iceberg, libgit2 bindings, in the future: an iceberg page, maybe other backends. pharo-graphics -> block/brick and upcoming graphical cool stuff pharo-gtools -> gtools + glamour, etc. pharo-nosql -> voyage family pharo-? -> I donât know, whatever
in the future, with the upcoming versions of iceberg + bootstrap, projects like iceberg, gtools, etc. will be âsubtreesâ of pharo-core so is good to have them well organised.
of course people are free to name their projects/organisation as they want, but I was trying to figure out a way for *us* :) (and since is very easy to change, we could just reorganise everything under pharo-project if we decide to put everything in just one repository).
Esteban
On 28 Apr 2017, at 10:11, Stephane Ducasse <stepharo.self@gmail.com> wrote:
esteban do we have a naming convention on github? pharo-xxx?
Stef
On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <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
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.
And here some info about the HOW TO (teams for Github are named "organisations") https://github.com/blog/674-introducing-organizations On Fri, Apr 28, 2017 at 6:07 PM Dimitris Chloupis <kilon.alios@gmail.com> wrote:
Why not make a Pharo team , we already have one for the books which also has a weird name "square bracker associates" , we should make a pharo team and put all the repos there so people can find them in one place
On Fri, Apr 28, 2017 at 11:31 AM Esteban Lorenzano <estebanlm@gmail.com> wrote:
Hi,
not really, but we want to promote pharo related stuff with the pharo prefix on the organisations (and those who in someway will fall under our umbrella)..
pharo-project -> core pharo pharo-vcs -> iceberg, libgit2 bindings, in the future: an iceberg page, maybe other backends. pharo-graphics -> block/brick and upcoming graphical cool stuff pharo-gtools -> gtools + glamour, etc. pharo-nosql -> voyage family pharo-? -> I donât know, whatever
in the future, with the upcoming versions of iceberg + bootstrap, projects like iceberg, gtools, etc. will be âsubtreesâ of pharo-core so is good to have them well organised.
of course people are free to name their projects/organisation as they want, but I was trying to figure out a way for *us* :) (and since is very easy to change, we could just reorganise everything under pharo-project if we decide to put everything in just one repository).
Esteban
On 28 Apr 2017, at 10:11, Stephane Ducasse <stepharo.self@gmail.com> wrote:
esteban do we have a naming convention on github? pharo-xxx?
Stef
On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <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
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.
On Fri, Apr 28, 2017 at 11:07 PM, Dimitris Chloupis <kilon.alios@gmail.com> wrote:
Why not make a Pharo team , we already have one for the books which also has a weird name "square bracker associates" ,
I don't think its weird. Square brackets "[ ]" to delineate blocks of code is one thing that distinguishes Smalltalk from those weird cult of curly brace "{ }" !! cheers -ben
we should make a pharo team and put all the repos there so people can find them in one place
On Fri, Apr 28, 2017 at 11:31 AM Esteban Lorenzano <estebanlm@gmail.com> wrote:
Hi,
not really, but we want to promote pharo related stuff with the pharo prefix on the organisations (and those who in someway will fall under our umbrella)..
pharo-project -> core pharo pharo-vcs -> iceberg, libgit2 bindings, in the future: an iceberg page, maybe other backends. pharo-graphics -> block/brick and upcoming graphical cool stuff pharo-gtools -> gtools + glamour, etc. pharo-nosql -> voyage family pharo-? -> I donât know, whatever
in the future, with the upcoming versions of iceberg + bootstrap, projects like iceberg, gtools, etc. will be âsubtreesâ of pharo-core so is good to have them well organised.
of course people are free to name their projects/organisation as they want, but I was trying to figure out a way for *us* :) (and since is very easy to change, we could just reorganise everything under pharo-project if we decide to put everything in just one repository).
Esteban
On 28 Apr 2017, at 10:11, Stephane Ducasse <stepharo.self@gmail.com> wrote:
esteban do we have a naming convention on github? pharo-xxx?
Stef
On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <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
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.
the reason that SBA exists is to get ISBN numbers for the books. It's an adhoc editor like Apress or O'Reilly, if you will. And it was created at the time of Squeak by Example, so probably a bit before Pharo. On 29 April 2017 at 03:04, Ben Coman <btc@openinworld.com> wrote:
On Fri, Apr 28, 2017 at 11:07 PM, Dimitris Chloupis <kilon.alios@gmail.com
wrote:
Why not make a Pharo team , we already have one for the books which also has a weird name "square bracker associates" ,
I don't think its weird. Square brackets "[ ]" to delineate blocks of code is one thing that distinguishes Smalltalk from those weird cult of curly brace "{ }" !!
cheers -ben
we should make a pharo team and put all the repos there so people can find them in one place
On Fri, Apr 28, 2017 at 11:31 AM Esteban Lorenzano <estebanlm@gmail.com> wrote:
Hi,
not really, but we want to promote pharo related stuff with the pharo prefix on the organisations (and those who in someway will fall under our umbrella)..
pharo-project -> core pharo pharo-vcs -> iceberg, libgit2 bindings, in the future: an iceberg page, maybe other backends. pharo-graphics -> block/brick and upcoming graphical cool stuff pharo-gtools -> gtools + glamour, etc. pharo-nosql -> voyage family pharo-? -> I donât know, whatever
in the future, with the upcoming versions of iceberg + bootstrap, projects like iceberg, gtools, etc. will be âsubtreesâ of pharo-core so is good to have them well organised.
of course people are free to name their projects/organisation as they want, but I was trying to figure out a way for *us* :) (and since is very easy to change, we could just reorganise everything under pharo-project if we decide to put everything in just one repository).
Esteban
On 28 Apr 2017, at 10:11, Stephane Ducasse <stepharo.self@gmail.com> wrote:
esteban do we have a naming convention on github? pharo-xxx?
Stef
On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <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
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.
-- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet
participants (7)
-
Ben Coman -
Damien Pollet -
Dimitris Chloupis -
Esteban Lorenzano -
phil＠highoctane.be -
Sean P. DeNigris -
Stephane Ducasse