VisualWorks Smalltalk 的分布式源代码管理
Smalltalk 令人烦恼的事情之一是，由于它管理源代码的方式，它（通常）需要自己的 VCS。 Squeak 和 Gemstone（至少在其 GLASS 版本中）有一个名为 Monticello 的 DVCS，效果还算不错。据我所知，VisualWorks 的主要 VCS StORE 只能在老式集中模式下工作。是否有类似于 Monticello 的系统可用于 VisualWorks？或者，我是否误解了使用 StORE 的正确方法？
One of the annoying things about Smalltalk is that it (usually) requires its own VCS, due to the way that it manages its source code. Squeak and Gemstone (at least in its GLASS version) have a DVCS called Monticello that works passably well. As near as I can tell, VisualWorks' main VCS, StORE, only works in old-fashioned centralized mode. Is there a system similar to Monticello available for VisualWorks? Alternatively, am I misunderstanding the right way to use StORE?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
虽然 Store 的结构不是分布式工具，但它可以以这种方式使用。大多数从事 VisualWorks 和 ObjectStudio 工作的工程师都使用本地存储库（在他们的办公室；大多数团队成员分布在不同的地理位置）。有合并和复制工具允许他们根据需要/期望将本地工作与“记录存储库”同步。
话虽如此，VW 有一个 Monticello 端口（因此，ObjectStudio 也有）。它唯一真正的问题是发布后，它不会与工具（浏览器）“谈论”发布状态。这是因为它主要用于维护 Seaside 端口，而不是作为 VW 的主线版本控制工具。
While Store is not structured to be a distributed tool, it can be used that way. Most of the engineers working on VisualWorks and ObjectStudio use a local repository (in their office; most of the team is geographically distributed). There are merging and replication tools that allows them to synch up their local work with the "repository of record" as required/desired.
Having said that, there's a port of Monticello for VW (and thus, for ObjectStudio as well). The only real issue with it is that after publishing, it doesn't "talk" to the tools (browser) about the publish status. That's because it's mostly use to maintain the Seaside port, and not as a mainline versioning tool for VW.