[cvsnt] Re: deleting a module from repository

abhishek jaiswal abhi658606 at yahoo.com
Mon Aug 30 10:34:58 BST 2004


Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


Hi everyone
 
For creating a new module in the repository, we have to first import the project to be kept under cvs through import command
e.g. cvs import -n C++/Project1
However before I or any team member check out Project1 module, following entry has to be made in module file of CVSROOT through check out and commit.
Project1     C++/Project1
 
Hence if it is required to delete entire module of Project1 ( suppose the project and its history is no longer required ) from the repository, then as suggested by you all, I should delete the Project1 folder from the Repository.
However it is also required to remove the above entry from the module file of CVSROOT
 
Now my question is like module file of CVSROOT, which are the files which are outside Project folder of Repository, that requires modification whenever a module is deleted from the repository
 
Hence in simple words, can anyone give me sequence to task required to remove a module from the repository
 
Thank you
 


Bo Berglund <bo.berglund at telia.com> wrote:
On Tue, 17 Aug 2004 15:29:25 -0600, "Siegfried Heintze"
wrote:

>
>Can you elaborate on your emphasis? Why might we be so reluctant to delete
>directories in the repository?
>

The CVS repository is a store that holds the complete history of all
source files of all of the controlled projects. As such it is supposed
to be able to bring back exactly any demanded old file situation (by
the use of tags) of any project and every single once existing
revision of any file.
In this context it is really a bad idea to go into the repository
(which resides in the server) and delete anything forcibly using
operating system tools. What this does is permanently destroy any hope
of being able to restore old files in the future. This is why Glen put
the emphasis on the delete suggestion.

On the other hand if you are experimenting in a test repository and
know what you are doing, then you can of course remove modules
(=directories) from the server as much as you like.

When you use the cvs remove command all it does is that it mark the
file in the repository as non-existing for future work, but it is
still there for retrieval of old tagged snapshots. The removal is
information that gets stored into the RCS file in the repository as
information.
And since CVS does not deal with folders in a source control sense
these cannot be removed at all, once created they stay there.

Hope this helps,

/Bo
(Bo Berglund, developer in Sweden)
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs

		
---------------------------------
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.


More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook