l.lunak at suse.cz
Wed Jun 25 15:43:33 BST 2003
On Monday 23 of June 2003 16:37, Sebastian Trueg wrote:
> > [Moved to kde-core-devel]
> > On Sunday 22 June 2003 12:48, David Faure wrote:
> > > On Sunday 22 June 2003 11:27, Daniel Molkentin wrote:
> > > > On Sunday 22 June 2003 11:00, Sebastian Trueg wrote:
> > > > >removed the "roaming user fix" from deller to get KDE 3.1 comp back.
> > > > >Please be aware that kdeextragear apps do not get released with the
> > > > > of the Kde packages and mostly should compile with the current KDE
> > > > > release (in this case: KDE 3.1)
> > >
> > > Huh? KDE-3.1 has readPathEntry/writePathEntry !!!
> > Hi Sebastian,
> > reverting is maybe the badest idea to solve a problem, since this also
> > means, that you loose the roaming support in KDE 3.2..
> > b) writePathEntry() in 3.1 (not in 3.1 BRANCH!) was broken and wrote
> > $HOME at the beginning of strings. This should be solvable with an
> #ifdef KDE_IS_VERSION(3,1,2)
> Are you sure this is a good solution? As far as I know KDE 3.1.x should be
> BC. So it's no problem to compile with KDE 3.1.2 and run with, say KDE
That's how TrollTech does it with Qt (and it's really annoying to wait so
longer for even the simplest new API call added, isn't it?). I was under the
impression that we didn't have any kind of this forward compatability. At
least I myself backported some new API calls in kdelibs that were needed for
backporting kdebase fixes.
> This way the bug will show. Am I right? Since a lot of users are
> installing rpm packages created by other users this may occur more than
> once. I never liked #ifdefs anyway. ;)
> So what can I do instead? I could provide my own implementation (some
> wrapper) for as long as K3b will be Kde 3.1 comp.. I think that would be
> the best solution.
SuSE CR, s.r.o. e-mail: l.lunak at suse.cz , l.lunak at kde.org
Drahobejlova 27 tel: +420 2 9654 2373
190 00 Praha 9 fax: +420 2 9654 2374
Czech Republic http://www.suse.cz/
More information about the kde-core-devel