how to handling read only cvs trees

[Jeremie Le Hen]

Gordon,

> The problem I am faced with is that there are new directories with new
> files (a lot) and these files are not included in the patch. I tried to
> 'cvs add' the directories, but I am not allowed the create the
> directories in /home/ncvs. Sure I just could fire up sudo to do the
> work, but I am afraid that cvsup, which I use to mirror the cvs
> repository, could delete them with the next scheduled run.
> 
> Has anyone a hint on how to handle this situation?

As a workaround, you can _try_ to modify CVS/Entries manually
(see my previous answer to Brooks).  If I add the file ``pouet'' :

% $ cp -R CVS CVS.bak
% $ touch pouet
% $ cvs add pouet
% $ diff -ur CVS CVS.bak
% diff -ur CVS.bak/Entries CVS/Entries
% --- CVS.bak/Entries     Thu Sep  8 16:54:00 2005
% +++ CVS/Entries Thu Sep  8 17:02:47 2005
% @@ -12,3 +12,4 @@
%  /profile.sh/1.9/Fri Jun 24 15:28:32 2005//
%  /make_patches.pl/1.3/Wed Jun 29 09:55:34 2005//
%  /profile.8/1.6/Mon Aug 15 19:22:38 2005//
% +/pouet/0/Initial pouet//
% Only in CVS: pouet,t

If it doesn't work, touch CVS/pouet,t, but I don't think this is
relevant.  In all cases, the CVS repository isn't change.

Regards,
-- 
Jeremie Le Hen
< jeremie at le-hen dot org >< ttz at chchile dot org >