Re: [Bug-gnubg] macport's portfile of the current gnubg

[Daisuke Takahashi]

Dear Michael,

Thank you. Therefore, it might be better to remove python variant and to depend 
on python by default. It is an implicit preparation for future gnubg, and as 
you pointed, it is not a heavy burden for most people; the dependence on python 
may be almost always satisfied.

By the way, is it possible to show a message like "pymysql or MySQLdb is 
required to connect to MySQL database" when a user tries to use MySQL without 
installing an appropriate python module? It would be helpful not only for 
macports people but also many other users.
Thank you very much.

Regards,
Daisuke Takahashi

On 2014/07/06, at 4:59, Michael Petch <address@hidden> wrote:

> 
> 
> On 2014-07-05 1:08 PM, Daisuke Takahashi wrote:
>> Basically I agree with you. When all the database codes are moved to python 
>> and c-code-sqlite implementation is dropped,
> 
> 
> I read what you wrote and I agree with it regarding how you are
> considering setting it up. I want to clear up a misconception I may have
> given. We don't intend to drop sqlite support, what I meant to say is
> that being more tightly integrated with Python in general may be what
> you will see more of in the future.
> 
> For instance I am considering introducing XG file format support via
> Python as my next pet project.
> 
> Thanks for you support of GNUBG, it is very much appreciated. It is nice
> to see someone spending time on the OS/X end of things. Although I do
> official builds with Macports on OS/X I never got around to maintaining
> the ports.
> 
> Thanks,
> 
> -- 
> Michael Petch
> GNU Backgammon Maintainer / Developer
> OpenPGP FingerPrint=D81C 6A0D 987E 7DA5 3219 6715 466A 2ACE 5CAE 3304