So far coding solo with git and filetree has been painless and
straightforward for me, I use github for public and gitlab for private
projects. I do not use configurations other than copy pasting one for
adding my project in Package browser. I do not use versioner because a
simple copy paste is eno
Le 11/05/2017 à 20:52, Stephane Ducasse a écrit :
Joachim
many people are using Pharo to develop ***COMPLEX*** Pharo applications
and it works. They use monticello and metacello and it works.
So you do not have to have Github to make great software in Pharo.
Now in addition many people are usin
Joachim
many people are using Pharo to develop ***COMPLEX*** Pharo applications and
it works. They use monticello and metacello and it works.
So you do not have to have Github to make great software in Pharo.
Now in addition many people are using github to build complex applications
with github.
> Am 11.05.2017 um 08:54 schrieb jtuc...@objektfabrik.de:
>
> Hi Norbert,
>
> thanks for your explanations.
> So it seems liek I should start by using Pharo6 and load Iceberg and just
> take a look.
>
Yes, iceberg has still some issues but is usable and it will evolve quickly. If
you are the
Hi again,
seems like I am too early. I just downloaded Pharo-60484 and loaded
Iceberg from the Catalog Browser and I get a Walkbacks as answer to
almost any click I perform ;-)
So I'll better start with the docs suggested in this thread to be ready
once Iceberg is ;-)
Joachim
Am 10.05.17
Hi Norbert,
thanks for your explanations.
So it seems liek I should start by using Pharo6 and load Iceberg and
just take a look.
Joachim
Am 10.05.17 um 10:34 schrieb Norbert Hartl:
Hi Joachim,
I think your timing is quite good. We had some changes in the last
years and it is getting bett
On Wed, May 10, 2017 at 1:56 PM, Joachim Tuchel wrote:
> Hi guys,
>
> please forgive me if this mail is a sign of ignorance. I am not a regular
> Pharo user and one of the reasons for this is that I didn't like most of the
> source management tools around Monticello. Coming from an envy background
Hi Joachim,
I think your timing is quite good. We had some changes in the last years and it
is getting better now.
Before we had only monticello. Monticello is a zip container that contains a
version number in the filename and prior version pointer inside the repository.
Regarding dependencies
Peter,
thanks for your view and links. Helps me sort things out and find what's
remained and keeps being relevant ;-)
Joachim
Am 10.05.17 um 10:08 schrieb Peter Uhnak:
Hi,
this is my (=not canonical) perspective
On Wed, May 10, 2017 at 07:56:19AM +0200, Joachim Tuchel wrote:
Hi guys,
ple
Hi,
this is my (=not canonical) perspective
On Wed, May 10, 2017 at 07:56:19AM +0200, Joachim Tuchel wrote:
> Hi guys,
>
> please forgive me if this mail is a sign of ignorance. I am not a
> regular Pharo user and one of the reasons for this is that I didn't
> like most of the source management
Stef,
thanks for answering.
Am 10.05.17 um 08:59 schrieb Stephane Ducasse:
Hi joachim
There is a distinction between managing projects and pharo. Pharo 60
is managed with Monticello.
Pharo 70 will not.
Okay, I came from the perspective of an application developer and not so
much as a contri
Hi joachim
There is a distinction between managing projects and pharo. Pharo 60 is
managed with Monticello.
Pharo 70 will not.
- git only - no monticello meta info any more - possible?
Yes people use that everyday. But Pharo is not manage like that (even if we
follow since years a git flow).
Hi guys,
please forgive me if this mail is a sign of ignorance. I am not a
regular Pharo user and one of the reasons for this is that I didn't like
most of the source management tools around Monticello. Coming from an
envy background, it feels like not being ready for prime time. Of course
yo
13 matches
Mail list logo