Re: unixodbc gui split

Nick Gorham <[email protected]> Sat, 16 Jan 2016 10:30:39 +0000
Newsgroups gmane.comp.db.unixodbc.devel
Message-ID <[email protected]>
On 16/01/16 05:04, Igor Korot wrote:
> Hi, Peter,
>
> On Fri, Jan 15, 2016 at 10:32 PM, Peter Lai <[email protected]> wrote:
>> 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.
> I believe you are wrong.

Belief will always be personal, though not always correct.
> unixODBC is a software for a client to make a client connect to DB server.
>
> Now as I said I am getting the error trying to compile the package:

Well, if you find the fix, by all means make it available.

-- 
Nick
_______________________________________________
unixODBC-dev mailing list
[email protected]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-dev