[Kde-games-devel] Re: Move Tagaro code into SVN?

[Parker Coates]

On Sun, May 1, 2011 at 00:43, Ian Wadham wrote:
> On Friday 15 April 2011 6:35:06 am Stefan Majewsky wrote:
>> On Wed, Apr 13, 2011 at 11:47 PM, Parker Coates wrote:
>> > If it means adding a new library for distributions to package, I think
>> > it has to go through kdereview, even if it does so with a "this is not
>> > a stable API" disclaimer. It's a relatively big change, so I think
>> > third parties (packagers, build system folks, translators, etc.)
>> > should have the opportunity to point out issues it may cause for them.
>>
>> Let's take this question to k-c-d. Some background for the new readers
>>
>> from my mail which started this thread:
>> > Would anybody mind if I moved the Tagaro source tree inside kdegames SVN,
>> > in a separate subdirectory? It will explicitly be described as an
>> > experimental and private library, with headers being installed only when
>> > the undocumented option -DINSTALL_HIGHLY_UNSTABLE_TAGARO_INCLUDES is
>> > given to CMake. [...]
>> > I know that this proposed procedure bypasses kdereview effectively, but
>> > big parts of Tagaro are already source-copied into kdegames somewhere,
>> > like TagaroAudio in Granatier and parts of TagaroInterface in Kolf. Also,
>> > KGameRenderer from libkdegames shares much with TagaroGraphics, so there
>> > is not much new code in there. Besides, I will of course issue a public
>> > review via kdereview when the library API is stabilized and goes public.
>>
>> P.S. Everyone is invited to review the code, of course. Look at the
>> current master branch of kde:libtagaro.
>>
> So where did we go with this?  I do not see Tagaro in KDE Reviewboard.

Excellent question. :)

> More to the point, I would like to use OpenAL sound and TagaroAudio in
> the KDE 4.7 version of KGoldrunner.  So how should I proceed?  Also,
> I just missed the Soft Feature Freeze by a couple of days.  Can I still
> get the feature in?  There should not be any new messages.

If the existing sound setup really is that bad, I'm pretty sure you
could consider the port to TagaroAudio a bugfix instead of a feature,
as long as it's done before the dependency freeze.

Parker