Re: Bug#1220: CVS postinst message rather verbose
From: Richard Kettlewell <email@example.com>
> I had a look at /usr/doc/cvs/INSTALL.gz. This tells you to create a
> master repository; I assume this means that the software is useless
> without one (BUT someone who actually knows CVS a bit might want to
> correct me here).
It's a little trickier than that. Yes, there has to be a repository
created before CVS works. But where and how many repositories there
are is very site-specific; that is to say, the software doesn't mandate
a Single Repository, so many sites use personal or project-level
repositories, and there may be no site-wide repository at all.
On the other hand, the CVS installations I manage have a single
site-wide repository, /usr/src/CVSREPO.
In general, I think the current setup (interactive prompting for a
repository location) is the right way to go.
> Therefore one must have been created by the end of
> the install, and there's no need to even tell the user about this,
> much less ask them.
Surely there should be at least enough interaction to determine
a location to create the repository; after all, the thing stores the
master copies of all CVS-controlled source codes there, and it could