Local Project File [Re: Extending the IProjectFileManager interface]

Matt Rogers mattr at kde.org
Sun Jul 8 04:34:03 UTC 2007

On Jul 6, 2007, at 8:23 AM, Jens Herden wrote:

>> There is such a file or even a set of file. We've introduced a .kdev4
>> directory where all things specific to an individual developers set
>> up should go. The .kdev4 directory takes the place of the single
>> project file. This means you can have a list of files or just one or
>> whatever fits your needs.
> I think this does not really serve our needs. The list of files is  
> needed by
> every user not only by one. So we would need to put this list in  
> the VCS as
> well. But I understand that everything under .kdev4 is a kind of  
> hidden and
> not supposed to get shared. That is why we thought we just stuff  
> this list in
> the main project file.
> Jens

IMHO, stuffing it in the main project file is incorrect. I understand  
you would think it would need to be sharable, but since initial  
project setup is (or at least should be) run only once, it would seem  
better to make this file list creation part of an import project  
wizard or some other similar thing. With a VCS for the project, this  
becomes ridiculously easy, since we just create the needed file list  
from what's checked out from the VCS but even without a VCS, we can  
just scan the directory indicated as the top level project directory  
and provide a list of checked files to use as the project and get the  
same effect.


More information about the KDevelop-devel mailing list