On Mon, 05 Dec 2011, Simo Sorce wrote:
> > > I like second approach more too. Although I think the best solution here
> > > would be to discard ipapython.dnsclient as is and use dnspython directly
> > > in our code. ipapython.dnsclient is not used on that many places in our
> > > code anyway.
> > >
> > > This way, we wouldn't have use our artificial dnsclient API in the
> > > proposed bridge but rather use (more standard) dnspython API and have
> > > access to all its native functionality.
> > Hm. Good idea. This though will have a toll for platforms where
> > dnspython is not yet available like various Red Hat Enterprise Linux
> > versions...
> RHEL can ship a version that bundles dnspython, we just need a
> conditional on import so that we import from ipasomething.dnspython if
> regular dnspython is not available.
Ok. From my perspective it is also much simpler to turn around and fix
usage of ipapython.dnsclient rather than mimic it on top of dnspython.
/ Alexander Bokovoy
Freeipa-devel mailing list