[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-freedink] Re: freedink for mac os x - follow ups

From: Sylvain Beucler
Subject: [Bug-freedink] Re: freedink for mac os x - follow ups
Date: Sat, 14 Mar 2009 18:42:59 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

On Fri, Mar 13, 2009 at 10:26:50PM +0100, Giovanni Davide Vergine wrote:
> Sylvain Beucler ha scritto:
>> Hi,
>> Apparently your work is awaited :)
>> http://www.dinknetwork.com/forum.cgi?MID=97713
>> I took the liberty to link your screenshot. I made sure that it didn't
>> contain personal information first.
>> Cheers!
> yeah :)
> finally, macport of freedink is available (5 minutes ago they committed  
> my port :))
> to use it, under mac os x:
> $ sudo port -d sync
> (port updating)
> $ sudo port install freedink
> (it will recursively install freedink-data)
> $ freedink
> or
> $ freedink -w
> :)
> I'm working on dfarc, i got dfarc window opened, i can resize it but i  
> can't click on buttons or checkbox. I think is something related with  
> wxwindows+macosx. I'll tell you more after some night of debugging :)
> cheers ;)

Cool. I forwarded to the forum.

I have a few comments:

- To check for SDL_ttf, here's the patch that will be in the next
  It does the check properly.

- I don't think changing paths is a good idea:
  FreeDink needs to run in a _consistent_ way across platforms, so
  patching the default paths is asking for troubles. Did you try using
  ./configure --prefix=/opt/local instead?

- freedink-data-inst is a binary package that doesn't include a few
  source elements, such as the source for the .midi.  It's not meant
  for packagers, who need to use the source tarball, otherwise you're
  violating the license (by redistributing GPL'd files without their

- Don't use freedink.org as a download location - the official
  location is http://ftp.gnu.org/gnu/freedink/, and it has mirrors
  (freedink.org doesn't, and I pay the bandwith =]).

More generally, if you find a problem in FreeDink, feel free to
discuss it and possibly send patches. I think it's safer for end users
when they all use the same versions, so they can freely move from one
environment to another, plus if improvements are shared, they'll apply
to too :)

What do you think?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]