Hi Otto,

2015-07-08 14:21 GMT+02:00 Otto Behrens <otto@finworks.biz>:

We have a .gitignore file that contains:
version
methodProperties.json

This is a bit drastic :)

��

So, we don't bother.

The side effects of this are:
Without methodProperties.json, you have the default author and
meaningless timestamp.
Without the version file, loading does not work properly. So we have a
script that generates version files for each package before we load
into the image. At first, this script counted versions for the package
and got all the info from the git repository. But this was too
expensive (because the file system became slow when traversing the git
repo to find the meta data). So now, we just generate a version file
with a fixed author, date & time now and a UUID & version number
derived from the SHA1 of the .package directory.

GitFileTree only derives the UUID from the SHA1 of the .package directory. It derives the version number from the number of versions in the git commit history.

��

We get all the meta-information directly from the git repo, using git
tools. This can be better with GitFileTree.

This is what GitFileTree does, with a crafted command for git log ;).

I'm interested in the "performance" issue reading versions from the git history you mention above. If you had the time to try with just installing GitFileTree and opening the repository, and checking: if it is slow, and if it gives you the right history.

��

So we really just use basics of Monticello & Metacello and do the rest
externally from the image. We need to explore the available tools
more.

This is one way to do it ;)

Thierry