Re: unixodbc gui split

This is the UNIX principle of KISS (keep it simple stupid). In a
server environment, having the GUI part is neither necessary nor
desirable. Core codebase provides the core functionality. As long as
the API is documented and the hooks are present/maintained, the GUI
code should be kept separate. This helps with development process
workflow: why result in extra version bumps of UnixODBC every time
some code in the GUI got changed? Why reduce portability/stability
just to keep add-on code? I suppose an argument could be made to use
Make flags to tell it whether to build the GUI or not.

On Fri, Jan 15, 2016 at 9:35 PM, Igor Korot <[email protected]> wrote:
> Hi, Nick,
> Sorry to write on the private email. I just don't know which unixODBC
> mailing list is still good...
>
> Have a quick question: what was the reasoning behind the GUI part split?
> I am running Gentoo and trying to compile the unixODBC GUI part it
> gives an error.
>
> It is very helpful to have the GUI part put back and ship it as one project.
>
> Thank you.
> _______________________________________________
> unixODBC-dev mailing list
> [email protected]
> http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev
_______________________________________________
unixODBC-dev mailing list
[email protected]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev