Deprecated askldap.c and askldap.h. Updated FAQ

git-svn-id: https://svn.alkaloid.net/gpl/ldap2dns/trunk@131 06cd67b6-e706-0410-b29e-9de616bca6e9
This commit is contained in:
Ben Klang
2005-12-07 23:45:26 +00:00
parent 581b3d082c
commit 205c8f02de
5 changed files with 18 additions and 1 deletions

View File

@@ -4,6 +4,7 @@ Version ?.?.? (next)
in a record.
Version 0.3.6 (latest)
+ New maintainer: Ben Klang <ben@alkaloid.net>
+ Fixed bug with duplicate OIDs in dns.schema from partially applied patch
+ Renamed schema file to ldap2dns.schema
+ Updated RPM specfile
@@ -18,6 +19,7 @@ Version 0.3.6 (latest)
+ Modified ldap2dns-conf to behave more like tinydns-conf
+ Altered default behavior (via ldap2dns-conf) to run ldap2dns as non-root
+ Updated FAQ
+ Deprecated askldap.c and askldap.h
Version 0.3.5 - 2005/11/30
+ Added support for DNS SRV records

15
FAQ
View File

@@ -12,6 +12,21 @@ own. You might also contact the author, Jacob Rief (jacob.rief@tiscover.com)
for more information but he is no longer interested in maintaing this work
so do not depend on him.
2) Why have you deprecated all that code?
2005-12-07 bklang
This is partially answered above, but to fully answer the question it's not
any comment or criticism of the original author. Really it is just code that
appears to me to be somewhat extraneous to what I consider to be the core
functionality of ldap2dns. That combined with my desire to focus on the core
functionality and not maintain this other work leads me to note the status of
that code to others who may use this package. The code may or may not work;
you are entirely on your own. If demand is sufficient some parts may come back
into the main tarball. However for now I leave it there in case anyone out
there wants it. It is unmaintained (at least by me) and should not be
considered stable or even working unless you audit it yourself.
You have been warned. Caveat emptor.
-- Old FAQ entry below (meaning is unclear to me -- 2005/12/07 bklang --

View File

@@ -13,7 +13,7 @@ sudo make DISTRIBUTION=suse rpm
if you are running Red Hat or SuSE respectively.
For updates and changes see http://projects.alkaloid.net
For updates, changes and some documentation, see http://projects.alkaloid.net
Please send any problem or success reports to the maintainer.