[KDE/Mac] Developing KDE on Mac

[Benjamin Reed]

2010/8/13 John Layt <johnlayt at googlemail.com>:

> If we claim to support a platform, then the KDE modules should build and run
> out of the box on that platform, no extra patches required. For the Mac
> project to eventually make that claim means _all_ patches need to be in
> mainline, there should never be patches required by MacPorts or Fink. People
> shouldn't have to go looking in other repositories just to get things to
> build and run, svn.kde.org is the canonical source. This may mean some parts
> of KDE are just not built or certain features are disabled until such time
> as a 'good-enough' solution is coded, but release branch should always build
> and run. If a crude hack is required short-term, then so be it so long as we
> know there's a more correct solution coming and the hack is not actually
> causing harm. Patches in Macports/Fink are OK as a short term fix or
> experiment, but should never be seen as a long-term or permanent solution
> for anything.

That's generally how I do them.  I try to push anything that isn't
about Fink specifically (path patches, stuff that auto-launches dbus
in a non-default location, etc.) upstream.

> Reviewboard now makes submitting patches even easier to do, and really easy
> to track what has been accepted and merged and what still needs work.

I have commit access, so if there's something sane, I'm happy to
commit it too...

> I would suggest your first course of action would be to progressively feed
> all the outstanding patches into mainline.

I'm working on (finally) packing up 4.5.0 for Fink, so I'll be doing
this, personally...


-- 
Benjamin Reed a.k.a. Ranger Rick
Fink, KDE, and Mac OS X development

Blog: http://www.raccoonfink.com/
Music: http://music.raccoonfink.com/