info-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: checking out a file (not a module)


From: Eugene Kramer
Subject: RE: checking out a file (not a module)
Date: Wed, 22 Nov 2000 16:24:33 -0800

There are several things you can do:

1. if you know your directory structure, you can create it in a sandbox area
with CVS subdirectories.Plase correct Root, Repository, and Entries file as
well as an empty Entries.static file. When you need to get a single file
from the repository, go to the directory where the file is and type 'cvs up
-d file'
2. In each directory create a directory keeper file ( .dir for example). Tag
all these files with a label, which is not used by regular files. To setup
an empty sandbox, checkout the hierarchy using the directory tag, then
remove all CVS/Tag files.

If you do not know the directory structure, you can use a 'cvs ls' patch.
You can also use my cvsls script, which I posted here some time ago.

The steps above are dirty hacks. Do not use them unless you absolutely sure
what you are doing. Better follow normal CVS practice and check out module
and work inside the module.

Eugene.

-----Original Message-----
From: ari gold [mailto:address@hidden
Sent: Wednesday, November 22, 2000 3:27 PM
To: address@hidden
Subject: Re: checking out a file (not a module)


the problem with this, is that it creates a new path.. for example, if i
have a directory 'dir' and a file in it 'foo' and i remove foo, dir is empty
(natch)..

if i then do, inside of 'dir', 'cvs co dir/foo' it will create another
directory 'dir' inside of 'dir'...

im looking to just create the file 'foo' by itself...

in case this is foggy, what im really trying to do is implement an empty
directory heirarchy.  the users (programmers) and i want their modules
(directories) to be empty.. then, when they do a checkout, it will take that
one file.  btw, in order to do this, i will, i suppose, need to make a
snappy build script that will know where to look for files and all.. this
"checking out a file (not a module)" trick is just the first step..

if anyone has any ideas on the subject, they would more than be
appreciated..

thanx again for all of your help.. hopefully soon enough ill be able to help
new folks and you all can sit back and relax with your wine and cheese..

~a



----- Original Message -----
From: "Eugene Kramer" <address@hidden>
To: "'ari gold'" <address@hidden>
Sent: Wednesday, November 22, 2000 6:17 PM
Subject: RE: checking out a file (not a module)


> cvs co path/file
>
> will do
>
> Eugene.
>
> -----Original Message-----
> From: ari gold [mailto:address@hidden
> Sent: Wednesday, November 22, 2000 2:44 PM
> To: address@hidden
> Subject: checking out a file (not a module)
>
>
> hello hello,
>
> i checked the faq and a few books i have and am scanning the cederqvist
but
> i still have no answer.. im looking to checkout just a file, not a module.
> the faq says "Though you *can* check out a file, you normally check out a
> module
> or directory." leads me to believe there's some command out there
> somewhere
> which'll let me check out just a file.. any ideas?
>
> thanx a bunch,
> ari
> address@hidden
>
>
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs


_______________________________________________
Info-cvs mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/info-cvs



reply via email to

[Prev in Thread] Current Thread [Next in Thread]