RE: request info

[Murukuti, Suren (GE Money, consultant)]

Hi Stuart,

I really appriciate for your response with the details.

1) Your previous version history is in your repository, so if you keep
the same repository or move the repository files over, you keep your
previous history.
         As per the acquisition we don't have any choice to keep the
repository where it exists today, I am planning to install CVS 1.11.23
in one of our Solaris 10 environment and migrate the CVS code base to
the new location. I am clear from your answer that I don't lose the
previous history. The another question as per migration I have is, Can I
use import to get the CVS code base into the new installation ? Any
suggestions from your side is highly appreciated.

2) I can't see any issues, they're only 6 point revisions different
between 1.11.17 to 1.11.23, you should be fine there.
        Thank you. I will move forward to use CVS 1.11.23

3) Typically in CVS you give users access to repositories, not
individual projects.
        If I decide to give access to users by repositories, Can you
direct or guide me how and where should I configure the users by
repository ?

4) If I would like to use SSH connection type, where should I configure
the public key for user in CVS ?

5) Is there any web interface for CVS admin activities, like creating
users, configuring ssh etc ?

Thanks a lot for your time and help.

Thanks and Regards
Suren


-----Original Message-----
From: Stuart Cooper [mailto:address@hidden 
Sent: Tuesday, March 24, 2009 7:05 PM
To: Murukuti, Suren (GE Money, consultant)
Cc: address@hidden
Subject: Re: request info

> Thank you for the information. I have one more quick question,

> I am going to get the projects source thoese are currently using CVS
> 1.11.17 and I would like to import into CVS 1.11.23 on Solaris. Do you

> have any idea that will keep all my previous version history. Do you 
> see any issue with migrating from CVS 1.11.17 to CVS 1.11.23 ? How can

> crate users for specific to project, is it something needs to be used
ACL ?

That seems like three questions.

1) Your previous version history is in your repository, so if you keep
the same repository or move the repository files over, you keep your
previous history.

2) I can't see any issues, they're only 6 point revisions different
between 1.11.17 to 1.11.23, you should be fine there.

3) Typically in CVS you give users access to repositories, not
individual projects.
You can use the "commitinfo" hook, or ACLs, to try and limit committers
on a project by project basis, but I'd be more inclined to use multiple
repositories and have a different set of users with access to different
repositories.

Cheers,
Stuart.