summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjascha@70a32439908b1e91c462a0b4cee819734bb0cea72017-08-31 00:09:19 +0000
committeradmin2017-08-31 00:09:19 +0000
commit1965d0fb063a4e7be28c7a33697ad8d69f495e6a (patch)
tree67164061f0e06f59e533fd422816bb3e8aa9eaa2
parentf235f21bee7f5133720027e38d13864b10667cd2 (diff)
Compatibility between different software versions
-rw-r--r--doc/forum/Compatibility_between_different_software_versions.mdwn1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/forum/Compatibility_between_different_software_versions.mdwn b/doc/forum/Compatibility_between_different_software_versions.mdwn
new file mode 100644
index 00000000..b2de3439
--- /dev/null
+++ b/doc/forum/Compatibility_between_different_software_versions.mdwn
@@ -0,0 +1 @@
+I'm just asking myself how (or if) we can guarantee compatibility between different versions of an application. Let's take "prosody" as an example. Even if we use the "DebianLike" property, there might be different versions of "prosody" in Debian Stable and Debian Unstable and therefore different configurations options available. Is there a way to catch those cases? Another example would be a "generic" property (which works for DebianLike and ArchLinux) for a specific software, but inside these distributions are different versions of the application. Even a "Prosody.installed" might be problematic, if the package has been renamed in a newer Debian release.