Bug 54489 - CVS/Entries doesn't exist in "src" directory after creating new project
Summary: CVS/Entries doesn't exist in "src" directory after creating new project
Status: RESOLVED FIXED
Alias: None
Product: kdevplatform
Classification: Developer tools
Component: cvs (show other bugs)
Version: 0.9.94
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-11 17:36 UTC by Barry Stokes
Modified: 2010-12-16 19:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Barry Stokes 2003-02-11 17:36:36 UTC
Version:           Alpha 3 (using KDE KDE 3.1)
Installed from:    Compiled From Sources
Compiler:          GCC 3.2.1 
OS:          Linux

I created a new project recently, telling it to use CVS for the version control. It created this fine, and the entries appeared in my CVSROOT etc. I then changed the source file in the SRC directory and tried to commit the changes. It then complained about there being no CVS/Entries and it not knowing anything about the file. I sorted this out by checking out the source tree from the repository, but surely it should be able to do this itself?
Comment 1 Amilcar do Carmo Lucas 2003-02-23 19:51:49 UTC
I can confirm this.
Comment 2 Yann Hodique 2003-03-24 20:25:35 UTC
now a script creates the CVS/* (or at least tries to :-))
Comment 3 Amilcar do Carmo Lucas 2003-03-25 16:42:20 UTC
I don't think it's a good idea!!! 
 
I think it would be better to: 
 
- Create the source files in some temporary directory, 
- Do 'cvs import' to get them into the CVS repository 
- Do 'cvs checkout' to get them out of the repository, into the project  
directory 
- Delete the files in the temporary directory 
(I think KDevelop 2.1.x does it like this already) 
 
Otherwise there can be some problems with odd cvs versions or cvs  
clashes with repository files 
(yes I had that once, but with KDevelop 2 I was able to detect that  
right away) with your technique 
 I would only detect that when I would try to commit something. 
 
But anyway your solution is better than nothing. :) 
Amilcar 
 
Comment 4 Mark J. Materna 2003-09-03 05:17:38 UTC
This this fix make into Gideon 3.0.0?? I'v got the same problem, using Gideon. This 
use to work fine in Kdevelop 2.1.x. 
Comment 5 Amilcar do Carmo Lucas 2003-09-03 09:40:56 UTC
Like the bug database says, it was fixed in 24-03-2003.
That means that the bug is solved in:
KDevelop 3.0 alpha 4
KDevelop 3.0 alpha 5
KDevelop 3.0 CVS HEAD

Please use CVS HEAD.
http://www.kdevelop.org/index.html?filename=branches_compiling.html