see the discussion in this thread ... initially GemStone needs to tolerate repositories that contain metadata-less packages ... then start considering ways to support and load metadata-less pacakges ...
GitFileTree's metadata-less mode means that the *.package/ monticello.meta/version file and all method property files are missing and no longer created ...
With the above patch, GemStone can properly read a metadata-less repo, but when it writes to the repo it will go ahead and create the metadata again ...
see the discussion in this thread ... initially GemStone needs to tolerate repositories that contain metadata-less packages ... then start considering ways to support and load metadata-less pacakges ...
GitFileTree's metadata-less mode means that the
*.package/ monticello.meta/version
file and all method property files are missing and no longer created ...