Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

On 15/06/2018 20:00, Tim Mackinnon wrote: > Phew - I can confirm that (unsurprisingly I guess) - just committing in > Iceberg (without ticking - push changes to origin/master) does then let > you easily overlay the same checked out project (typically > ./iceberg/ProjectName) in a tool like VSCode

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Phew - I can confirm that (unsurprisingly I guess) - just committing in Iceberg (without ticking - push changes to origin/master) does then let you easily overlay the same checked out project (typically ./iceberg/ProjectName) in a tool like VSCode or IntelliJ where you can then also commit

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Tod/Norbert - I won’t shy away from answering your comments on this - but if its ok - lets move that conversation to a new thread. I don’t want to distract away from how one actually does some form of atomic checkin (and I’m talking a small one - one Smalltalk class, one associated text file).

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

> On Jun 15, 2018, at 2:05 AM, Esteban Lorenzano wrote: > > > >> On 15 Jun 2018, at 10:29, Tim Mackinnon > > wrote: >> >> >> In many parts of the dev world - every commit should be shippable, meaning >> atomic - particularly with the use of CI systems (Travis,

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

> Am 15.06.2018 um 10:29 schrieb Tim Mackinnon : > > > In many parts of the dev world - every commit should be shippable, meaning > atomic - particularly with the use of CI systems (Travis, Gitlab etc) that > build on every commit. > To be honest I don’t like such comments. Do you have a

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

> On 15 Jun 2018, at 10:29, Tim Mackinnon wrote: > > > In many parts of the dev world - every commit should be shippable, meaning > atomic - particularly with the use of CI systems (Travis, Gitlab etc) that > build on every commit. but then, you mean every *push* should be shippable :)

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Hi Tim, On Fri, Jun 15, 2018 at 10:31 AM Tim Mackinnon wrote: > > In many parts of the dev world - every commit should be shippable, meaning > atomic - particularly with the use of CI systems (Travis, Gitlab etc) that > build on every commit. > > Of course you can choose to work a different way

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

In many parts of the dev world - every commit should be shippable, meaning atomic - particularly with the use of CI systems (Travis, Gitlab etc) that build on every commit. Of course you can choose to work a different way - but our tools shouldn’t force a very common practice to be awkward,

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

2018-06-15 8:19 GMT+02:00 Esteban Lorenzano : > > > On 15 Jun 2018, at 08:11, Norbert Hartl wrote: > > > > Am 14.06.2018 um 13:12 schrieb Thierry Goubier >: > > Hi Norbert, Tim, > > 2018-06-14 11:33 GMT+02:00 Norbert Hartl : > >> >> >> Am 14.06.2018 um 10:30 schrieb Tim Mackinnon : >> >> Hi -

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

2018-06-15 8:11 GMT+02:00 Norbert Hartl : > > > Am 14.06.2018 um 13:12 schrieb Thierry Goubier >: > > Hi Norbert, Tim, > > 2018-06-14 11:33 GMT+02:00 Norbert Hartl : > >> >> >> Am 14.06.2018 um 10:30 schrieb Tim Mackinnon : >> >> Hi - yes I’m pleased you check out the entire tree, although

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

> On 15 Jun 2018, at 08:11, Norbert Hartl wrote: > > > > Am 14.06.2018 um 13:12 schrieb Thierry Goubier >: > >> Hi Norbert, Tim, >> >> 2018-06-14 11:33 GMT+02:00 Norbert Hartl > >: >> >> >>> Am 14.06.2018 um 10:30 schrieb Tim

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

> Am 14.06.2018 um 13:12 schrieb Thierry Goubier : > > Hi Norbert, Tim, > > 2018-06-14 11:33 GMT+02:00 Norbert Hartl : >> >> >>> Am 14.06.2018 um 10:30 schrieb Tim Mackinnon : >>> >>> Hi - yes I’m pleased you check out the entire tree, although currently it’s >>> a bit confusing that you

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

2018-06-14 15:39 GMT+02:00 Tim Mackinnon : > Yes - I’m a fan of small checkins (not always great at it, but I strive > for it) - and yes, the issue I’ve had is the same as what Thierry mentions > - my Smalltalk code is tied to an external file which has some rewrite > rules that depend on the

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Yes - I’m a fan of small checkins (not always great at it, but I strive for it) - and yes, the issue I’ve had is the same as what Thierry mentions - my Smalltalk code is tied to an external file which has some rewrite rules that depend on the classes I have in my image. I could possibly

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Hi Norbert, Tim, 2018-06-14 11:33 GMT+02:00 Norbert Hartl : > > > Am 14.06.2018 um 10:30 schrieb Tim Mackinnon : > > Hi - yes I’m pleased you check out the entire tree, although currently > it’s a bit confusing that you do (fortunately this does give the > possibility that we can checkout images

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

> Am 14.06.2018 um 10:30 schrieb Tim Mackinnon : > > Hi - yes I’m pleased you check out the entire tree, although currently it’s a > bit confusing that you do (fortunately this does give the possibility that we > can checkout images and other resources that an Pharo application might rely >

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

BTW, addFilesToIndex: will not add files to the git index immediately, it will do it just before a commit only. On Thu, Jun 14, 2018 at 11:03 AM Guillermo Polito wrote: > addFileToIndex: and addFilesToIndex: are still there... > > We of course have support for changing and committing arbitrary

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

addFileToIndex: and addFilesToIndex: are still there... We of course have support for changing and committing arbitrary files (actually, pharo code at the end are just arbitrary files!). The difficult part is to bring a consistent UI to life for it... On Thu, Jun 14, 2018 at 10:43 AM Tim

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Ooooh - I didn’t know about #addToIndex: that sounds like a possible workaround to my problem (but not a generic solution though). BTW - I don’t want this to be a criticism, I’m loving the tools and their possibilities! Tim Sent from my iPhone > On 14 Jun 2018, at 09:36, Peter Uhnák wrote:

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Wait... so it is no longer possible to #addtoIndex: external files from Pharo? I thought that this functionality was supposed to be preserved. Peter On Thu, Jun 14, 2018 at 10:30 AM, Tim Mackinnon wrote: > Hi - yes I’m pleased you check out the entire tree, although currently > it’s a bit

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Hi - yes I’m pleased you check out the entire tree, although currently it’s a bit confusing that you do (fortunately this does give the possibility that we can checkout images and other resources that an Pharo application might rely on - without having to resort to the Seaside FileLibrary

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Just to complement Esteban's answer: - Iceberg checks out in disk more than the src directory because you **may** want to edit files from the command line, and after long discussions we did not want to forbid that. Actually, just to put everybody in perspective, at first the idea was to not have

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

> yeah… but is a lot of work and no time just right now. > long term, it would be cool to manage everything from iceberg. > but reality check, is a huge amount of work so it has to come step by step. Fair enough - its pretty cool we’ve got this far, and I guess the onus is on the rest of us to

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

> On 13 Jun 2018, at 22:44, Tim Mackinnon wrote: > > Esteban - so I don't then understand why iceberg (usefully in my view) checks > out more than the src directory, if it’s only focusing on the Pharo blob? > > I’m guessing that by knowing where the src is, you are just committing that >

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Esteban - so I don't then understand why iceberg (usefully in my view) checks out more than the src directory, if it’s only focusing on the Pharo blob? I’m guessing that by knowing where the src is, you are just committing that part of the tree with libgit? Perhaps from a pragmatic first step

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

hi, > On 13 Jun 2018, at 16:50, Tim Mackinnon wrote: > > Hi - my second attempt at using Pharo with Git has proven very satisfying (I > saw the potential in phase 1, but it was often difficult to understand what > was happening and the workflow to use). > > One thing that has come up a few

Re: [Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

On 13/06/2018 11:50, Tim Mackinnon wrote: > Hi - my second attempt at using Pharo with Git has proven very satisfying (I > saw the potential in phase 1, but it was often difficult to understand what > was happening and the workflow to use). > > One thing that has come up a few times for me

[Pharo-users] Why doesn't Iceberg checkin other assets (scripts) but does check them out?

Hi - my second attempt at using Pharo with Git has proven very satisfying (I saw the potential in phase 1, but it was often difficult to understand what was happening and the workflow to use). One thing that has come up a few times for me however - and its something that using git nicely