Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Programming / CodeWarrior / March 2004



Tip: Looking for answers? Try searching our database.

CVS on local machine

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Michael Charleston - 02 Mar 2004 12:14 GMT
Dear gurus,

Pertinent info:
  running OS X 10.3.2 on G4 powerbook
  Metrowerks Pro 8.3

I would like to set up CVS on my local machine for a project I'm
developing by myself, but for the life of me I can't figure out what the
settings should be.  I've made a directory /usr/local/cvsrep for the
repository, but what should the path be in the CodeWarrior settings?  
Have tried variations on a theme of

  CVSROOT=:local:myusername@localhost:/usr/local/cvsrep

but all I get when I try to connect is the familiar

  "Version Control was unable to resolve the path to the database,
  please check your preferences."

error.

Can anyone help please?
Much obliged,
Mike
MW Ron - 02 Mar 2004 15:53 GMT
>Dear gurus,
>
[quoted text clipped - 16 lines]
>
>error.

Once the project has been added/imported into the local repository,
create a new directory and checkout the project directory, either
through the IDE VCS menu or command line CVS.  The act of checking out
the files/folders will create the CVS folders that store repository
information.

Ron

Signature

Announcing  CodeWarrior Development Tools for Windows v9.2
http://www.metrowerks.com/MW/Develop/Desktop/Windows/Professional/Default.htm
Ron Liechty - MWRon@metrowerks.com - <http://www.metrowerks.com>

Michael Charleston - 02 Mar 2004 19:48 GMT
> >Dear gurus,
> >
[quoted text clipped - 24 lines]
>
> Ron

That did it, finally.  Thanks Ron!
Alexey Proskuryakov - 03 Mar 2004 09:15 GMT
On 02.03.2004 15:14, in article
mcharleston-7EEFC2.12141402032004@news2.cableinet.net, "Michael Charleston"
<mcharleston@onetel.net.uk> wrote:

>  CVSROOT=:local:myusername@localhost:/usr/local/cvsrep

 You may want to consider that it is usually strongly recommended to never
use local mode of CVS: you will most likely end up with a corrupted
repository.

 A safer way is to use a client/server "pserver" mode, even if there is
only one CVS user and one machine for client and server.

 You may also want to consider Perforce, which is much better than CVS and
comes with a free 2-user license.

- WBR, Alexey Proskuryakov
Miro Jurisic - 03 Mar 2004 15:46 GMT
>   You may want to consider that it is usually strongly recommended to never
> use local mode of CVS: you will most likely end up with a corrupted
> repository.

Where did you get that?

>   A safer way is to use a client/server "pserver" mode, even if there is
> only one CVS user and one machine for client and server.

CVS over SSH should be preferred to pserver.

meeroh

Signature

If this message helped you, consider buying an item
from my wish list: <http://web.meeroh.org/wishlist>

Alexey Proskuryakov - 04 Mar 2004 08:22 GMT
On 03.03.2004 18:46, in article
macdev-861666.10463403032004@senator-bedfellow.mit.edu, "Miro Jurisic"
<macdev@meeroh.org> wrote:

>>   You may want to consider that it is usually strongly recommended to never
>> use local mode of CVS: you will most likely end up with a corrupted
>> repository.
>
> Where did you get that?

 Well, you can always search Google for "CVS local mode repository corrupt"
to get a ton of hits :). I think that I read this in one of the CVSNT
installation HOWTOs, which says "local: Should never be used by CVS clients
as accessing raw repository files will result in corrupt files and dangling
file locks": http://www.ypsolog.com/docs/comp/windows/cvsnt.html

 Actually, this is quite obvious. If you expose your full repository to the
client, a client's bug can ruin it. Furthermore, if you use an advanced tool
which starts multiple threads to access CVS, you are virtually guaranteed to
have problems at some moment, even if no bugs are triggered - local mode
doesn't allow simultaneous access at all.

>>   A safer way is to use a client/server "pserver" mode, even if there is
>> only one CVS user and one machine for client and server.
>
> CVS over SSH should be preferred to pserver.

 For a single-machine setup?!

- WBR, Alexey Proskuryakov
Miro Jurisic - 04 Mar 2004 13:38 GMT
> On 03.03.2004 18:46, in article
> macdev-861666.10463403032004@senator-bedfellow.mit.edu, "Miro Jurisic"
[quoted text clipped - 6 lines]
>
>   For a single-machine setup?!

On OSes that come with an SSH server (which is pretty much everything except for
Windows), it is easier to set up and more secure than pserver.

meeroh

Signature

If this message helped you, consider buying an item
from my wish list: <http://web.meeroh.org/wishlist>

Miro Jurisic - 04 Mar 2004 13:50 GMT
>   Well, you can always search Google for "CVS local mode repository corrupt"
> to get a ton of hits :). I think that I read this in one of the CVSNT
> installation HOWTOs, which says "local: Should never be used by CVS clients
> as accessing raw repository files will result in corrupt files and dangling
> file locks": http://www.ypsolog.com/docs/comp/windows/cvsnt.html

I did. All I found was a lot of articles about corrupting your repository files
by using incorrect -k flags, and one article (the one you refer to) that is
windows specific and makes a passing and unsubstantiated mention of possible
corruption. I am sorry, but reading the rest of that article did not impress me
with its technical accuracy, and it states upfront that it specifically refers
to an enhanced Windows version of CVS. I have no reason to believe this bug
exists in other versions of CVS.

>   Actually, this is quite obvious. If you expose your full repository to the
> client, a client's bug can ruin it.

Actually, when you run the server, the same cvs binary runs on the server
anyway, so a bug in the client or the server can still eat your repository. I
have not seen this happen in over 8 years of using CVS.

> Furthermore, if you use an advanced tool
> which starts multiple threads to access CVS, you are virtually guaranteed to
> have problems at some moment, even if no bugs are triggered - local mode
> doesn't allow simultaneous access at all.

The local mode uses filesystem locking in precisely the same way the remote mode
does. If you are using a Windows port in which that locking is broken, that is
not a fault of CVS, but of the incompetent people who ported it.

meeroh

Signature

If this message helped you, consider buying an item
from my wish list: <http://web.meeroh.org/wishlist>

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.