Esteban Lorenzano <estebanlm@gmail.com> writes:
Most of our problems here is because we insist on being interchangeable between git and mcz. While treating git as âjust another repositoryâ can feel appealable in certain cases (for example, in the super-uncommon way of handle vm building we have, when we use git and Eliot uses squeak source, then we are kind of a mirror), this is not the most common usage: if you start a project on git, you are expected other contributors use git too⦠same as in any other SVC tool (there is not compatibility between SVN, HG, GIT, etc.)
Of course, it looked like a good idea at the beginning, but now I think is counterproductive (is the kind of ideas that are great at the beginning because it provides security/confortability to users, but with time demonstrate obsolete).
What we actually need is tools that can load configurations from different sources (for example, I have a project in git who uses seaside and I want a configuration who loads bothâ¦). But⦠guess what? WE ALREADY HAVE IT!!!! Metacello is perfectly capable of doing that. Gofer is capable of doing that. Heck, even monticello is capable of doing that as long as we do not pretend their are interchangeable!
So, again⦠what we actually need is to accept reality: we do not need all that metadata in 99% of cases!
do you propose to stop using Monticello completely? Just have a snippet to load code from a directory and store packages to a directory? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill