<html> <head> <meta content="text/html; charset=windows-1252" http-equiv="Content-Type"> </head> <body bgcolor="#FFFFFF" text="#000000"> <div class="moz-cite-prefix">On 11.11.2016 15:25, Christian Heimes wrote: </div> <blockquote cite="mid:228f2a0e-a3a6-92ec-8e59-c45f4283999d@redhat.com" type="cite"> <pre wrap="">Hello, I have released the first version of a new design document. It describes how I'm going to improve integration of FreeIPA's client libraries (ipalib, ipapython, ipaclient, ipaplatform) for third party developers. <a class="moz-txt-link-freetext" href="http://www.freeipa.org/page/V4/Integration_Improvements">http://www.freeipa.org/page/V4/Integration_Improvements</a> Regards, Christian </pre> <fieldset class="mimeAttachmentHeader"></fieldset> </blockquote> Hello, I have a few questions: 1) dynamic platform files Currently all RHEL/fedora-derived platforms work with the same rhel/fedora packages. How do you want to achieve this with dynamic platform files, do you want to keep mappings between platforms and platform file? What about distributions that have in /etc/release just mess? 2) if I understand correctly, you want to separate client installer code and client CLI code. In past we had freeipa-admintools but it was removed because it was really tightly bounded to installed client. Do you want to revive it and make it independent? 3) why instead of environ variable we cannot have specified paths with priority where IPA config can be located? For example: 1) ./.ipa.conf 2) ~/.ipa.conf 3) /etc/ipa/default.conf <-- as last resort </body> </html>