跨应用程序共享文件
我们有一个需要在多个应用程序之间共享的通用功能。我们已经有了一些内部库，我们将具有定义良好的接口的通用代码放入其中。但有时，某些代码（通常是单个或几个 .cpp 文件）会出现问题，因为它不适合现有库，而且太小而无法创建新库。
我们当前的版本控制系统支持文件共享，因此通常这些文件只是在使用它们的应用程序之间共享。我倾向于认为这是一件坏事，但实际上，它非常清楚，因为您可以准确地看到它们在哪些应用程序中使用。
现在，我们正在转向 svn，它没有“真正的”文件共享，有这个 svn:externals 东西，但是在使用时跟踪文件共享的位置仍然很简单它？
我们可以创建一个“垃圾”库（或文件夹）并将此类文件暂时放在那里，但这始终是同样的问题，它使依赖项跟踪变得复杂（哪个项目使用此文件？）。
否则还有其他好的解决办法吗？在你们公司是如何运作的？
We have a common functionality we need to share among several applications. We already have a few internal libraries, into which we put common code with a well-defined interface. Sometimes, though, there are problems with some code (typically a single or a few .cpp files) as it doesn't fit into an existing library and it is too small to make a new one.
Our current version control system supports file sharing, so usually such files are just shared between the applications that use them. I tend to consider it a bad thing, but actually, it makes it quite clear, as you can see exactly in which applications they are used.
Now, we are moving to svn, which does not have "real" file sharing, there is this svn:externals stuff, but will it still be simple to track the places where the files are shared when using it?
We could create a "garbage" library (or folder) and put such files there temporarily, but it's always the same problem that it complicates dependency tracking (which project use this file?).
Otherwise, are there other good solutions? How does it work in your company?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
为什么不在 SVN 中创建一个名为“Shared”的文件夹并将共享文件放入其中呢？您可以从那里将共享文件包含到您的项目中。
更新：
似乎您正在寻找一个跟踪依赖项的第三方工具。
Subversion 和依赖项
Why don't you just create a folder in SVN called "Shared" and put your shared files into that? You can include the shared files into your projects from there.
Update:
Seems like you are looking for a 3rd party tool that tracks dependencies.
Subversion and dependencies
您只能通过查看所有存储库来找出文件的使用位置。
You can only find out where a file is used by looking at all repositories.