[dev-context] Versioning system for modules
patrick at gundla.ch
Thu Mar 11 14:30:44 CET 2010
Am 11.03.2010 um 14:20 schrieb Norbert Preining:
> On Do, 11 Mär 2010, Patrick Gundlach wrote:
>> what are the requirements for version controlled systems? What are the usecases? It is hard to decide which versioning system to use without knowing who needs it and when.
> Is that a question coming out of thin air?
No, there is a discussion on the main context mailing list and I don't want to discuss this with a broad audience.
I don't want to answer the question before knowing the exact question.
> I would suggest git.
Me, too. I use git for almost everything, but it could be that an automatic svn repository via webdav could suffice. That way the users don't have to do anything at all, no installation of a SCM, no commands to learn, etc.
As far as I understand the "problem": we need version controlled modules. Why? Who would go back in time? The module authors? Other users? The minimals-distribution-Mojca?
What interface do these people need? How often do they need access to the SCM? Should we get rid of the files on the modules section?
Lot's of questions, and I don't know the answer.
>> Patr... (can't type the rest of my name right now, too complicated)
> Too much Sake? Too much wine? ;-)
No, just a bit upset. But I'll calm down.
> Even after some glasses of Sake
That looks all greek to me :-)
Patrick (<- better now)
More information about the dev-context