mathieu wrote:
Should the daily tarball of the CVS include the CVSROOT.
pro: permits people to get their complete tree as they want.
against: provide files useless for people just interested in using the
software
I have no clear opinion, can you give me your. I'm going to start by
including the CVSROOT.
It should include all information, including CVSROOT.
That said, most files are site-specific, except history and val-tags.
With more words : people had recurrent trouble with tarballs from
Savannah due to CVSROOT/config pointing lock_path to a site-specific
place; on the other hand, you can't correctly parse history and branches
without CVSROOT/history and CVSROOT/val-tags (even if that can
theorically be reconstructed from the RCS files).
Anyway, for backup purposes, it's easier to archive everything and
have some doc explaining the few tricks to rehost a CVS repository. It's
fine the way it is now :).
