| Summary: | CVSROOT Not set when creating a new project | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Barry Stokes <barry> |
| Component: | general | Assignee: | KDevelop Developers <kdevelop-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Barry Stokes
2003-02-11 18:00:57 UTC
You don't need CVSROOT, if a repository is already checked out (and there is a CVS/ directory) cvs will use that. During checkout and checkins just use the "-d" parameter (check the cvs manpage for details). You can set the parameters for cvs in the gideon project options. I don't see this as a fixed bug. The problem is that cvs is expecting there to be a CVSROOT defined. So obviously there isn't a CVS directory, or it cannot be used properly. As KDevelop set up the CVS stuff, I would have assumed it would have done it so that CVS was in a usable state. Considering that this is not the case, then there is still a bug somewhere, whether it's CVSROOT nor being set, or KDevelop not setting it up correctly. I would have thought that I should not need to do things such as looking in the man pages for cvs, as I assumed that KDevelop would handle such things properly. *sigh* Bug 54489 is a bug which stays in the database until it is fixed. Your request for setting $CVSROOT doesn't make sense for KDevelop, so I mark this as resolved. Use "-d" or wait until 54489 is resolved or try to fix it yourself and send a patch to the list. Thanks, Harry |