docs source compatibility (was: [Rosegarden-devel] minor patches)

[Scott Wheeler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 03 May 2003 20:58, Chris Cannam wrote:

> Really?  And is it this documentation thing that's breaking it?

Yep.  Apparently it worked with 3.1, but not 3.1.1.

> I have three machines I build Rosegarden on regularly, and they're all 
> running KDE 3.0.x.  One of them will probably be upgraded to 3.1 in 
> the next few days.  Obviously for me anything that breaks a 3.0 build 
> is quite useless, but if it won't build on 3.1.x without it then we 
> have a real problem.  (I thought some of the other RG developers were 
> using much more recent KDE versions than I was, but I could be 
> mistaken.)

Yeah, the problem seems to be that the line with Docbook v4.1 works for KDE 
3.0 -> KDE 3.1.0, and v4.1.2 works from KDE 3.1.0 -> HEAD.

> I'm assuming as this is an XML DTD declaration we can't just do 
> anything quite like an #ifdef based on KDE version.  What do the KDE 
> developers recommend doing in order to maintain source-level 
> compatibility between KDE 3.0 and 3.1/3.2 for these files?

Yes, I consider this to be a source compatibility issue, so I'm CC'ing 
kde-core-devel.  Basically if something compiled on KDE 3.0, it should 
compile with all 3.x versions of KDE, and this was obviously not the case for 
KDE 3.0 -> KDE 3.1.1.

(Ok, Lauri, who broke it?  ;-) )

Cheers,

- -Scott

- -- 
Well this should cheer you up for sure.  You see I've got your old ID and 
you're all dressed up like The Cure.
- --Ben Folds Five, "Battle of Who Could Care Less"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+tB3BQu0ByfY5QTkRAo0EAJ9C+1m7Ihv6u0OmAEpYeyBqOW4qYACgsZIW
broBE9/Hgrqn2WvQUwofWmg=
=bAZs
-----END PGP SIGNATURE-----