Dale,
you're right, the monticello.meta directory is kept, in part because I
wasn't sure I could get rid of some of the information in some files in
that directory (dependencies, initializers).
Since those files don't usually create conflicts with git, it seemed Ok.
Thierry
Le 29/06/2016 01:11, Dale Henrichs a écrit :
On 6/28/16 2:16 PM, Thierry Goubier wrote:
Dale,
I'm sure it is possible. Wait, wait! If you have in your .filetree
"Metadata" : "false" then this is fine and it has switched to the
metadata-less mode.
To see the changes on disk, you need to save a new version of your
packages, that should be all.
I just tried and that works.
1- remove the GitFileTree repository from your image
2- write the property "Metadata" : "false" in the .filetree on disk
3- re-add the GitFileTree repository (local)
4- modify then save one of the repository packages
5- look on disk: no more monticello.meta/version!
Note that I had no packages in the image linked to that repository at
1-, because I'm not sure the simple removal would have really removed
the repository singleton object.
Well I've found the culprit: MCFileTreeWriter>>addString:at:encodedTo:
ensures that monticello.meta directory exists...
Of course as I reread your comment "no more monticello.meta/version" I
will have to say that I've only been looking at whether or not the
monticello.meta directory existed or not ... I equate "no monticello
meta data" as no monticello.meta directory and you interpret it as "no
monticallo version file" ... well I can live with that ... I swore that
I saw version files being updated in some of my experiments ... but now
that I know that I should only look at the monticello.meta/version file,
I will try yet again ...
Yes
Thanks for you patience and help ...
Dale
