Version: (using KDE Devel) Installed from: Compiled sources OS: Linux When adding 'Sub projects' to a project with CVS support, there should be a dialog asking whether to add it to the repository as well. If not this is what happens: 1) Add subproject 2) Add target for the subproject 3) Try to add a file for this target and you get asked if you want to add the file to CVS 4) Choose Yes. This fails because the directory itself isn't in cvs already! -- and you get an error saying the CVS directory was not found. The add to CVS dialog is _everywhere_ else, I guess it should be here too :) Although, it's annoying sometimes when it comes up and a) you don't have cvs support enabled in the project and b) it asks when it shouldn't because the directory isn't under cvs control. Haven't tried with the new cvsservice plugin but I imagine it would have similiar issues if not already addressed.
*** Bug 62997 has been marked as a duplicate of this bug. ***
It should be fixed with vcs/cvsservice: it no more bother the user about requesting to add files to a subproject which has not committed to repository yet. To commit a new subproject (and its dir) do as following (from file tree view): 1) select the subproject dir and rmb -> cvsservice -> add 2) select evey file in the subproject dir you want to add to repository and rmb-> cvsservice -> add 3) (while the files are still selected) rmb -> cvsservice -> commit 4) fill the dialog and have your files committed :-) Could be closed now? :-)
The annoying part is fixed (I think) but the really confusing and bad usability part is not it seems (??) The whole point of the bug was to actually give a dialog of adding to the repository as soon as _any_ new directory gets created in your project -- this includes sub-projects which get handled as another directory. If it is not the case it not only requires the 4 (!) additional steps you noted but also this scenario: 1) You've added many directories off and on ... how do you know which has been added and have not? I don't think the vcscoloring handles that correct? And even if it did it would require _another_ step to "Sync with Repository" (can that be automated by the way so the user doesn't have to do it?) so you get the information you need. But thanks for the other fix :) That's still needed for directories that the user really didn't want in the repository
As far as I can see this is fixed. Cvs unfortunately doesn't allow to do a recursive cvs add, so files have to be added individually. And kdevelop has no way to know wether a new subproject was created, so the automake manager would have to do a lot work for IMHO too little gain.