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 however - and its something
> that using git nicely highlights, there are many non-smalltalk assets in my
> project that don’t need to live in the image (like Seaside FileLibraries were
> trying to do) but do need to be versioned and be part of my project. Common
> examples are server config files, images and even the playground history
> files that are useful to pull up when on another computer.
> [SNIP]
> It strikes me that this is the kind of thing that git integration should
> bring to us?
Of the mentioned benefits of using Git (or any other file based SCM) was
exactly that of versioning "external" assets.
You could do that with filetree/gitfiletree.
But I guess that given then tight integration of Iceberg with git and
the Pharo workflow, to "sync" ("commit") external files, these should be
visible to Iceberg as well, and should be added for staging on each
commit, which means that Iceberg should have a "file explorer" of some
sort integrated into its GUI.
Regards,
--
Esteban A. Maringolo
