Closed brauner closed 7 years ago
I'm assuming the next step for this is to change the version check function to understand the -devel suffix too?
At which point we should rip out the LXC_DEVEL define check from the go-lxc code tree entirely as it'd just lead to false positives at this point.
So this is just part of a branch that wanted to implement runtime liblxc detection but it's not as easily done as it occurred to me at first because of conditional compilation requirements. This is tricky in so far as you always have the danger of having mismatch between what go-lxc was compiled against vs what it is currently using as runtime dependency.
I can show you the full branch, one sec.
liblxc will now append "-devel" (e.g. 2.1.0-devel") when LXC_DEVEL is true. From a semantic versioning perspective liblxc is doing a saner thing than go-lxc with appending "-devel" instead of " (devel)" but we shouldn't break existing user. They might already rely on " (devel)" so let's keep it.
Signed-off-by: Christian Brauner christian.brauner@ubuntu.com