[despammed] kdevelop.kdevelop

[Hendrik Kueck]

So here is a general question about making changes regarding project files:
How important is backward compatibility with existing project files? Say 
some settings are moved from .kdevelop to .kdevses; is it acceptable 
that users existing settings in their .kdevelop files get lost/ ignored 
in the process and they have to redo their settings? Or should there be 
code that migrates settings if an old style .kdevelop file is encountered?

Hendrik

PS: I posted a patch a couple of days ago hoping that somebody would 
review and submit it to CVS, but did not get any feedback on the list or 
per email. I assume nobody read my posting to the part where I asked for 
this. So, could somebody please submit it. Alternatively: what is the 
procedure for getting access to the CVS?


F at lk Brettschneider wrote:
> Hi!
> Seems someone has removed the .kdevelop project file for KDevelop3 from 
> CVS.
> I think it should be in CVS again since it's a proof of concept if that 
> file is able to be shared in a team development environment.
> 
> Any user-specific stuff should be moved to the common session file 
> (~/.kde/share/config/kdeveloprc) or to the project-specific session file 
> (.kdevses). Further details on this are at the bottom of white paper 
> http://developer.kde.org/documentation/library/cvs-api/kdevelop/html/howToAddPlugins.html 
> ..
> 
> Any objections for a reanimation?
> 
> CU
> F at lk
> 
> 
> 
> _______________________________________________
> Kdevelop-devel mailing list
> Kdevelop-devel at barney.cs.uni-potsdam.de
> http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
> 
> ----------------------------------------------
> Filtered by despammed.com.  Tracer: SAA116801066779368
> Remember: you can forward any spam that slips through the filters
> to the abuse desk here at Despammed.
>