On Tue, 2008-09-23 at 13:53 +0200, Holger Levsen wrote: > is libnss-ldapd a fork of the libnss-ldap package or upstream fork? > libnss-ldapd uses a different versioning scheme than nss-ldap, so I'm a bit > lost evaluating whether you incorporate upstream fixes or not, and if, how... > > Your upstream changelog only lists the 252 release of nss-ldap in the > beginning and then thats it.
nss-ldapd was forked from nss_ldap 251 and only some minor fixed from nss_ldap were incorporated. With recent releases there is hardly any common code left as nss-ldapd has been mostly rewritten. So that would make nss-ldapd an "upstream" fork. > Originally I simply wanted to ask you this question, but now I've decided to > file it as a wishlist bug, as I think the description should be made clearer > to answer this question :) Good idea. Perhaps the second sentence should be replaced with something like: This is a fork from libnss-ldap implementing structural design changes to fix, amongst other things, problems related to host name lookups and name lookups during booting. (I mention libnss-ldap instead of nss_ldap because that is the name the package is known for in Debian) Do you have a better suggestion? Anyway, thanks for the bug report. -- -- arthur - [EMAIL PROTECTED] - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
