作为附带项目，CentOS还建立了其发行版的用户更新包，但这些库默认情况下不启用，因为他们可能破坏兼容性。
As a side project, CentOS also builds updated packages for the users of its distributions, but the repositories containing them are not enabled by default as they may break upstream compatibility.
我知道这两个额外的符号十分讨厌；我也知道这将会破坏向后兼容性。
I know the extra two characters are annoying; I know this will break backwards compatibility.
这种类型的API的任何变化都有可能破坏向后的兼容性，引起大量问题。
Any change to an API of that kind will break backwards compatibility and cause a lot of trouble.
如何确保一定级别的兼容性，以减少对应用程序的破坏呢？
How do you ensure a level of compatibility to reduce disruptions to the applications?
他们是否应该应用一个可能破坏旧型号计算机兼容性的补丁？
Should they apply a patch that may break compatibility with older machines?
添加元素和重新对操作排序不会破坏WSDL中的向后兼容性。
Adding elements and reordering operations doesn't break backward compatibility in WSDL.
除非是根本性的变更，都应该有可能对服务进行版本控制，使其不破坏与现有客户端的兼容性。
Barring fundamental changes, it should be possible to version services without breaking compatibility with existing clients.
这不是AIX二进制兼容性语句的破坏，而是不支持32 位内核扩展。
This is not a breakage of the AIX binary compatibility statement, but a fact that 32-bit kernel extensions are not supported.
我不喜欢破坏HTTP的向后兼容性，而且没有更好的协议去支持REST的工作。
I don't want to break backwards-compatibility with HTTP, and there is no better protocol available for the business of doing REST.
我猜想，blogosphere内的一些帖子会让Python的支持者也会误认为其中的某些变更—例如对向后兼容性的打破—具有破坏性的影响。
I'm guessing from reading entries in the blogosphere that many Pythonistas consider some of the changes-such as the backwards compatibility break-deal breakers.
在文件破坏向后兼容性时，应该能够检测并报告错误。
Detect when the file breaks backward-compatibility and report an error.
Ext4文件系统被设计为具有向前和向后兼容性，但它具有许多新的高级特性(其中的一些特性破坏了兼容性)。
The ext4 file system is designed as a backward - and forward-compliant replacement for ext3fs but with many new advanced features (some of which break the compatibility).
原因主要有两个：第一，如果先优化再做兼容性，你的优化很可能破坏了兼容性。
There's two major reasons for this. First, if you optimize and then work on compatibility, you're very likely to optimize in ways that break that compatibility.
微软在数年前破坏了VisualBasic的兼容性。
A few years ago, Microsoft broke compatibility for Visual Basic.
多接口允许对象的版本控制，而不会破坏已上线对象的兼容性：要创建一个新的版本，我们会在现有对象上添加新的接口。
Multiple interfaces permit versioning of objects without breaking on-the-wire compatibility: to create a newer version, we add new interfaces to existing objects.
多接口允许对象的版本控制，而不会破坏已上线对象的兼容性：要创建一个新的版本，我们会在现有对象上添加新的接口。
Multiple interfaces permit versioning of objects without breaking on-the-wire compatibility: to create a newer version, we add new interfaces to existing objects.
应用推荐