> We (Volker, Metze, GÃnther, Michael and me) talked about these two functions
> again. Maybe we should try to get them into 3.2.0 to avoid bumping the
> library version number in 3.2.1.
I thought about all this a bit more and noticed that we would also need
to implement a wbcChangePassword() in order to later support pam_winbind
And as my last mail explained we also need wbcLogonUser() and have it
complete so that pam_winbind can use it later.
We should aim to get as much done before 3.2.0.rc1, but it could be that
we find some other missing features, which require
an update of the library version.
Maybe we should think about using symbol versioning,
That would mean we can extent the API without breaking old applications.
And at least rpm based systems would be able to handle this easily, e.g.
metze@SERNOX:~> rpm -q --provides libattr
libattr = 2.4.28-38
metze@SERNOX:~> rpm -q --requires attr
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PayloadIsBzip2) <= 3.0.5-1
Does anyone knows if debian also supports dependencies based
on the different symbol versions within a shared library.
The patch is really trivial, but we need to make sure it doesn't
break the build on some systems:
diff --git a/source/exports/libwbclient.syms
index f1e68b4..8c12c1a 100644
@@ -1,4 +1,4 @@