info-cvs
[Top][All Lists]
Advanced

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

Re: Ignoring files and directories when checking out


From: Russ Sherk
Subject: Re: Ignoring files and directories when checking out
Date: Wed, 30 Nov 2005 07:54:15 -0500

Matthew,

Again, please take the time to change the subject line in your responses.  The question has been answered in the original thread.

On 11/29/05, Matthew Herrmann <address@hidden> wrote:
Hi Sanjay,

I'm guessing these are things like user documentation or instructional
videos etc. To handle this situation, store the data as normal files with
versions on a server. Ie:

\\server\projname\res\BigFile1.dat.7

Then, as part of the process that requires the file (perhaps the release
process?), include:

"copy /y \\server\projname\res\BigFile1.dat.7 .\BigFile1.dat"

to get a copy of the file. You could make this more efficient, but this will
do the job. When you need to update the file, make a file called
BigFile1.dat.8, and update the script to copy that file instead. If you're
using remote servers, you can use scp or pscp to copy the data instead. Then
there is no need for partially tagged repositories which can become a
maintenance nightmare.

While it is sometimes  useful to keep files out of cvs (we do this for some documentation), it is still a maintinance nightmare.  Probably moreso than creating a 'big file only' cvs module.

To be super abstract, you can fetch the files from a folder specified by an
environment variable, similar to the CVSROOT variable. In that case, you can
move your repositories to a different server and still be able to fetch
historical versions reliably.

 Another good point.  Now all developers: a) must have access to the server b) know the full path to the bigFiles c) know which version of the file goes with which source version (cvs tagged).  This can all be automated... but is it worth it?

Matthew Herrmann
________________________________

Director
Far Edge Pty Ltd
http://www.faredge.com.au/


-----Original Message-----
Message: 7
Date: Tue, 29 Nov 2005 12:16:10 +0530
From: Sanjay Goel < address@hidden>
Subject: Re: Ignoring files and directories when checking out
To: Jim Hyslop <address@hidden>
Cc: address@hidden
Message-ID:
        <address@hidden>
Content-Type: text/plain; charset="iso-8859-1"

I have a few big data files (>100 MB) that I would want to keep on the cvs
server. But then every developer will have to checkout that file when they
do a root level checkout. Since most of the developers will not need this
file, I wanted a way to mask these files, as VSS does support the masking
feature. Tagging and removing seems like a workable hack, though not really
clean.

Thanks
Sanjay

On 11/29/05, Jim Hyslop < address@hidden> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Sanjay Goel wrote:
> > Hi all, I am a newbie to this group. I beg your pardon in advance in
> > case this question has been asked before (though I couldn't find it
> > after searching the archives) Is it possible to mark some files and
> > directories as masked/ignored so that when I checkout a parent level
> > directory, these files/directories don't check out?
>
> No. Just don't check them in, in the first place ;=)
>
> Well, strictly speaking that's not true. You could tag the files and
> then 'cvs rm' them. Any time you do want to get them, you'll have to get
> them by tag.
>
> What exactly are you trying to accomplish? Maybe there's another way to
> get what you want.
>
> - --
> Jim Hyslop
> Dreampossible: Better software. Simply.     http://www.dreampossible.ca
>                  Consulting * Mentoring * Training in
>     C/C++ * OOD * SW Development & Practices * Version Management
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFDi4VxLdDyDwyJw+MRAhkdAJ9i7UIh566mcPpo94ll8rRDjwERzgCgiLv7
> dlXHd7tKPV3wZVRwfb9s94g=
> =4t60
> -----END PGP SIGNATURE-----
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.gnu.org/pipermail/info-cvs/attachments/20051129/8a0d5f25/attach
ment.html

------------------------------

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


End of Info-cvs Digest, Vol 36, Issue 51
****************************************



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


On 11/29/05, Jim Hyslop <address@hidden> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sanjay Goel wrote:
> I have a few big data files (>100 MB) that I would want to keep on the cvs
> server. But then every developer will have to checkout that file when they
> do a root level checkout. Since most of the developers will not need this
> file, I wanted a way to mask these files, as VSS does support the masking
> feature. Tagging and removing seems like a workable hack, though not really
> clean.

Partition your repository better. Get your developers out of the habit
of doing root level checkouts - it makes it quite limiting for you, as
you have just found out. This means you have to also get out of the
mindset of "one project, one repository" - a repository is quite capable
of tracking hundreds of separate projects.

Move the files into a different directory, then either use a cvs module
(see the manual on 'modules file') or a script to explicitly check out
those files when needed.

- --
Jim Hyslop
Dreampossible: Better software. Simply.     http://www.dreampossible.ca
                 Consulting * Mentoring * Training in
    C/C++ * OOD * SW Development & Practices * Version Management
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDjEijLdDyDwyJw+MRArzBAJ9CzqeGqTuRFD8zx0WvPrgnU6yLlQCfboxk
0X5VLXA2iBqeGeQyoyopynA=
=y72E
-----END PGP SIGNATURE-----



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


reply via email to

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