Hi all - sorry for the slow reply and thanks for your input here. Briefly, simplicity is the overriding criteria here.
fontconfig should be ok but should be optional. I'm not actually sure what it gives us at this point - for a game a particular font is integral to the look and feel. Please merge if you think it is useful.
For box2d it is best to keep a fixed version as part of np. Even a slight difference in the physics from version to version can make or break some levels. I've already broken some levels by incorporating the latest version.
Thanks again,
Tim
----- Original message -----
> Hello, Leo and Tim!
>
> On Sat, Jan 23, 2010 at 11:11:41PM +0100, Leo 'costela' Antunes wrote:
> > I imagine your focus on the Maemo platform will mean most Debian bugs
> > won't really interest you guys, but as long as I can muster up some
> > platform-agnostic patches, would you consider them for inclusion?
>
> Tim is the project leader, so he has the final word on what goes in and
> what stays out. I'll be happy to merge your patches and see if they work
> on both Maemo 4 and Maemo 5, and I guess Tim will be okay with the
> patches if they don't disrupt the functionality on Maemo.
>
> > Case in point: I've already patched the source to optionally use
> > fontconfig instead of the hardcoded font file (I'm distributing this
> > font separately, though, to keep the game's visual identity intact).
>
> fontconfig seems to be available at least on Maemo 5, so I don't think
> that this is a problem.
>
> > Another thing I'm working on is a patch to enable building with the
> > system-wide libbox2d, but this still needs some work before it can be
> > integrated. Would such changes be accepted?
>
> We would have to package libbox2d for Maemo, but as it uses the same
> packaging format as Debian, we can probably take the package from Debian
> and create a Maemo package from it with just some minor modifications.
>
>
> Greetings,
> Thomas
>