Lines Matching refs:Repository
159 - The CVS "default branch" is the Repository source for the
287 can even aim it at the whole Repository ($CVSROOT), if you have to. It
578 physically move the file from the Attic to the main Repository
585 set repos = `cat ./CVS/Repository` mv $repos/Attic/filename,v
588 (If you use relative paths in your Repository files, that first line
589 becomes: set repos = $CVSROOT/`cat ./CVS/Repository`)
592 Repository, "update -A" will make it appear in your working directory
702 execute raw "rcs" commands on the Repository, taking advantage of
703 CVS's ability to find the files in the Repository.
706 Repository, which is not generally safe unless you know exactly what
820 Repository while you do this. If they commit something while you are
912 <module> can be a relative path within the Repository.
1029 merges committed changes from the Repository into the working file.
1113 sections of the Repository containing files that will all be worked on
1117 how to lay it out in a Repository. After that the modules file is
1148 Actual Repository directory structure: (from $CVSROOT down)
1159 Repository layout using module names (and aliases containing module
1199 the Repository:
1262 Repository must be managed separately, creating additional work.
1265 Repository. A few additional considerations:
1267 It is a good idea to start by creating a single Repository and split
1269 really necessary. I would only create a new Repository if the data is
1270 completely disconnected from the rest of the main Repository.
1275 of my way to create a single Repository. It is much easier to manage.
1278 Repository using symbolic links and/or remote mounts.
1280 Each Repository is completely distinct. You can't check out modules
1284 pathnames), then they are in the same Repository.
1288 when you change focus to another Repository. If you work with multiple
1290 pathnames in the ./CVS/Repository file, since most commands (other
1294 ./CVS/Repository files, you must always be careful to set your
1300 unrelated files. This is not a fanciful example -- a Repository is
1306 4. Who should administer the Repository and manage the modules file?
1321 Modules and Repository admin was mostly left to me. I never found a
1358 Repository activity. When something went wrong, I notified the contact
1392 5. Isn't disk space a big factor? CVS copies files out of the Repository,
1469 revisions from the Repository, not the revision you wanted to start
1499 You must decide where to set up a Repository.
1501 Though you can construct a Repository tree structure using links and
1506 CVS does not support a truly distributed Repository. You can have
1511 Initially, a Repository takes about same amount of disk space as the
1530 one or more "Repository Administrators" who will be responsible for
1531 maintaining the Repository structure, administrative files and the
1584 Set your $CVSROOT environment variable and create the Repository
1588 You'll need to edit the Repository control files created by
1622 2. Explain: "RCS file /Repository/module/file.c,v is in use"
1628 Go into the Repository and look for files with names similar to
1669 is no RCS file in the Repository to back it up.
1674 When you try to check out a piece of the Repository with:
1692 If the Repository files you are trying to check out or update are
1698 6. Why did a Repository file change from <file>,v to ,<file>,?
1857 Additionally, if you are restricting "read" access to the Repository
1955 " + Setting up and Managing the Repository"
1957 1. What do I do first? How do I create a Repository?
1961 Then create a Repository by executing "cvs -d init". (This works with
1993 There are eight Repository control (or "database") files of interest
2000 against pathnames within the Repository and
2004 When you execute "commit", CVS passes the Repository pathname for each
2047 3. Is there any other state stored in the Repository besides in the
2050 Only in the RCS files. The Repository holds exactly two things: the
2056 4. How do I put sources into the Repository?
2058 There are three main ways to put files in the Repository:
2063 Repository and the *only* way to handle source releases from a 3rd
2068 This is how to add new files and directories to the Repository, a few
2071 You can move RCS files directly into the Repository.
2074 move arbitrary ",v" files into the Repository. The only "state" in the
2075 Repository other than within ",v" files is in the required CVSROOT
2076 directory at the top of the Repository.
2080 5. What file permissions should I use on (and in) the Repository?
2095 - Set all the directory permissions in the Repository to 775.
2114 - Repository directory permissions to 770. (or 2770)
2145 6. How do I structure my Repository?
2147 The Repository holds your software. It can be all interrelated or it
2160 In other words, you should structure your Repository to match your
2182 the interrelations between all portions of your Repository in your
2190 The "modules" file represents a published interface to the Repository
2191 set up by your Repository Administrator. If s/he did a creditable job,
2211 file in the Repository, "remove" the old version so it winds up in the
2222 Move the files and directories in the Repository to the new names.
2242 same time, you must edit the pathname stored in the ./CVS/Repository
2250 file, but not in the Repository. For the old file, "update" prints:
2283 When you "commit" a removed file, CVS moves the Repository's matching
2284 RCS file into a sub-directory named "Attic" within the Repository.
2295 10. Is it OK to remove anything from the Repository?
2297 In general, removing anything from the Repository is a bad idea. The
2302 stored in the Repository:
2304 CVSROOT files (Repository control files)
2306 The Repository will work without any of them, but you should
2360 within the Repository, check out that directory and start working.
2364 12. Can I move RCS files with branches in them into the Repository?
2379 13. Can I use raw RCS commands on the Repository?
2381 You can use raw rcs commands directly on the Repository if you take a
2382 little care. The Repository itself contains no "CVS state" (as opposed
2388 See 4D.7 on RCS/CVS sharing of the Repository and Section 3B on the
2397 into the Repository as described above.
2401 15. How do I limit access to the Repository?
2403 There are all sorts of ways to restrict access to Repository files,
2410 The best form of Repository control is a combination of:
2421 touch important sources the "owner" of the CVS Repository must be a
2430 Repository if that helps.
2439 groups of machines to keep (for example) the Engineering Repository
2451 16. What are the Repository Administrator's responsibilities?
2454 Repository and monitor its size and control files.
2458 Examining the Repository once in a while to clean up:
2460 Trash files left by misguided developers who mistake the Repository
2464 $CVSROOT/CVSROOT directory, every file in the Repository should be an
2488 Maintaining the other Repository control files: commitinfo, loginfo,
2502 Repository files. Ideas:
2514 17. How do I move the whole Repository?
2517 works great. If the Repository does not contain any symlinks, which it
2521 Repository) by replacing the old location with a symbolic link to the
2531 The Repository itself contains no references to its own name, except
2534 directly in the Repository, you'll have to change the pathnames to
2535 point to the new Repository location.
2538 files (./CVS/Repository and ./CVS/Root) in every working directory
2539 ever checked out from the previous location of the Repository you just
2544 If all ./CVS/Repository files in all working directories contain
2549 from the new Repository after the move.
2551 Use "find . ( -name Repository -o -name Root )" and a PERL or shell
2552 script to run through all the ./CVS/Repository and ./CVS/Root files
2557 18. How do I change permissions on a file in the Repository by using a CVS
2561 bits on the Repository file are inherited from the original source
2562 file, while the write bits on the Repository file are are turned off.
2566 Repository using CVS (or RCS) commands. You have to change the
2567 permissions on both your working file and on the Repository file from
2572 permissions of the Repository file, minus any "umask" bits you have
2612 2. Can I edit the RCS (",v") files in the Repository?
2638 3. Can I edit the ./CVS/{Entries,Repository,Tag} files?
2643 If you move pieces of your Repository around it can be faster to edit
2644 all the ./CVS/Repository files rather than checking out a large tree.
2795 The other way to rename a magic <branch_tag> is to edit the Repository
2814 7. How can I allow access to the Repository by both CVS and RCS?
2820 a shared Repository has to take second place to system integration
2824 If you really must allow routine RCS access to the CVS Repository, you
2825 can link an RCS sub-directory into a piece of the Repository:
2827 ln -s /Repository/some/directory/I/want RCS
2833 If a file was originally added to the Repository by "import" and has
2840 move them into the Repository. That way they won't have Vendor
2888 Repository to replace a deleted file. If CVS changes your file in an
2899 on the files in the Repository. See 4D.17 for some more about
2908 to match the timestamp stored on the revision in the Repository's RCS
2963 some of the information by referring directly to the Repository files.
2974 "update" command finds a file in the Repository that is not in the
2976 "new" file out of the Repository and adds the filename to the Entries
2979 Added to the Repository from another working directory.
2988 ./CVS/Entries.Static. If a Repository file is found in *neither* file,
2993 don't contain all files in the corresponding Repository directory. In
2995 would bring more files out of the Repository than the original
3007 12. Why did I get the wrong Repository in the loginfo message?
3013 Configured CVS to use absolute pathnames in the ./CVS/Repository
3018 Typed the "commit" command in one Repository with your $CVSROOT
3022 the ./CVS/Repository file (or in the "-d CVSrootdir" override), but
3074 Put *no* users in the "cvsg" group. You can put Repository
3081 Make sure every file in the Repository is in group "cvsg":
3124 Repository) these questions:
3134 every file in the Repository? (This is useful if you want to program
3186 access to the Repository?
3189 and commits it, the Repository will have a file in it that is
3220 To add a new directory to the Repository or to register the desire to
3221 add a new file to the Repository.
3225 the file to the Repository, you must then "commit" it.
3373 Then mark the RCS file in the Repository so that keyword expansion is
3379 Repository's RCS file, you no longer need the sticky option. You can
3546 the latest revision in the Repository *and* the timestamp in the
3559 a Repository (",v") file. Don't do it unless you are absolutely
3584 Repository. It provides a compact name space and the ability to
3624 but figures out what Repository files to look at by reading the files
3643 must provide two pathnames: where to find it in the Repository and
3668 same directory hierarchy as in the Repository. The same kind of
3678 files with the ability to structure the Repository so that consistent
3680 the Repository Administrators to set up a modules file that describes
3681 the software within the Repository.
3690 The ./CVS/Repository file in each working directory contains a
3691 pathname pointing to the matching directory within the Repository. The
3696 will move along with it. As long as you don't move the Repository
3827 To store new revisions in the Repository, making them visible to other
4014 of the Attic into the associated Repository directory and "update -A"
4073 revisions in the Repository?
4087 3. How do I display what changed in the Repository since I last executed
4154 to know what revisions from your Repository they started with
4159 branch of your Repository. They would need to remember to checkin the
4299 Repository, an event work recording. "tag" was intended for adding and
4340 * Last modifier of file/Repository X? -c -l -[fp] X
4343 * History of file/Repository/module X: -[fpn] X
4360 etc) in the file. If your Repository is mounted through NFS onto
4376 The first "import" to a particular file within the Repository creates
4378 "import"s of the same file within the Repository append a new revision
4413 where <repos> is the relative directory pathname within the Repository
4417 anything. It is easier to remove bogus files from the Repository than
4455 as well to move pre-existing RCS files into Repository directories.
4457 You can create a whole Repository tree by copying a directory
4458 hierarchy of normal source files directly into the Repository and
4558 new copies from the Repository:
4576 Then delete the imported files from the Repository and re-"import" the
4630 against the one you have in your Repository. If the Vendor has removed
4654 What I generally do is to close the Repository for a while and make
4655 changes in both the Repository and in a copy of the vendor release
4669 into the Repository.
4671 Other than the CVSROOT directory, the Repository consists entirely of
4672 directories of ",v" files. The Repository contains no other state
4675 See Section 4B, on Setting up and Managing the Repository.
4683 are managing a large Repository, any care taken up front will save you
4694 matches the structure of the current Repository.
4727 Repository than to run a subset "import" to catch just the ignored
4733 Repository. The directory <new source> must be at
4735 the <repos> you give is within the Repository. (I
4773 CVS creates a new file in the Repository. You don't have to do
4828 archive. Along with the tags you placed on the Repository before the
4848 Repository before starting the import, you should have no trouble
4953 Removing a few extraneous files from the Repository is a lot easier
5163 Repository, allowing no way to retrieve anything other than by module
5240 in the Repository.
5243 do a cvs commit, and then do a _rmdir dir_ in the Repository.
5271 set repos = `cat ./CVS/Repository`
5274 (If you use relative paths in your Repository files, that first line
5275 becomes: set repos = $CVSROOT/`cat ./CVS/Repository`)
5283 some revision will be taken from the normal Repository area and from
5308 module directly in the Repository.
5312 2. Why use "rtag"? It assumes no one is changing the Repository.
5316 whole-Repository actions, which occur at major release boundaries.
5518 Repository.
5582 Repository tree structure) with the following revisions:
5651 in after the release tag was stamped onto the Repository.
5673 the whole Repository, then delete the old one.
5776 "cvs update" merges changes made to the Repository, since your last
5783 revision from the Repository.
5787 for files you have modified that have not changed in the Repository.
5798 the Repository).
5803 Repository.
5806 Repository.
5809 Repository.
5813 consider the Repository as the branch and your working directory as
5828 Nothing on your branch changed in the Repository.
5855 new directories that have been added to the Repository.
5869 Repository matches your BASE revision when the files themselves don't
5952 <tag> from the Repository files. "update -r <tag>" will delete a file
5989 pathname changes in the Repository. A general solution is a difficult
6353 Tell your Repository Administrator to create a module covering the
6363 a directory by substituting its relative path within the Repository
6425 5. I just created a new file. How do I add it to the Repository?
6432 To add <file> to the Repository, type:
6446 Retrieving changes made to the Repository on the *same* branch you are
6448 command tries to merge work committed to the Repository by others
6465 have committed changes to the Repository since your last "checkout",
6468 file in the Repository. It will print:
6476 your BASE revision (the revision you retrieved from the Repository in
6485 committed changes to the Repository, but in different sections of the
6486 file, CVS will merge the changes stored in the Repository since your
6490 RCS file: /Repository/module/<file> retrieving revision 1.X retrieving
6504 RCS file: /Repository/module/<file> retrieving revision 1.X retrieving
6531 To "tag" the latest revision on the Main branch in the Repository, you
6533 directly on the Repository.)
6586 If you are the Repository Administrator, see 4B.16 on Administrator
6679 Those that work directly on the Repository or its administrative
6722 The file doesn't exist in the Repository until you "commit" it, but
6796 Repository into your modified working file.
6804 in the Repository contains revisions up through 1.4.
6884 A Repository Administrator uses this to add site-specific files and
6895 usually don't end up in the Repository.
6913 the ignore list. A Repository administrator can use this to override,
6924 command line) a sub-directory within a Repository hierarchy. For
7016 clean up in the Repository.
7055 the Repository, or by using the equivalent: "cvs admin".
7086 permissions to limit access to the Repository.
7102 Repository. I call these persons Repository Administrators. They
7103 should have set up a Repository and "imported" files into it.
7106 testing CVS, then *you* are the Repository Administrator.
7108 If you are a normal user of CVS ask your Repository Administrator what
7113 If you *are* the Repository Administrator, you will want to read
7130 use the "checkout" command to copy files from the Repository to your
7146 CVSROOT Absolute pathname of the head of your Repository.
7211 Repository".
7221 Yes. Unless the directory exists in the Repository, "update" will skip
7233 2. How do I add new sub-directories to the Repository?
7244 and will create both a matching directory in the Repository and a
7252 Repository.)
7265 directory. Each directory in the Repository stores its deleted files
7281 Copy the RCS (",v") file directly in the Repository.
7325 directory are really in the Repository?
7329 the Repository, preceded by a '?'. To register foreign directories,
7333 You could also checkout your module, or the Repository directory
7340 really want to see all the files that aren't in the Repository, you
7349 within the Repository, but it will also display each file not in the
7350 Repository preceded by a '?' character.
7402 CVSROOT directory inside the Repository into a form that is usable by
7418 Say you want to split , which already in the Repository, into three
7421 Copy the RCS (",v") files directly in the Repository, creating the
7488 changing the underlying RCS files in the Repository.
7512 up-to-date with the Repository, already tagged with the same string,
7804 1. What are "The Repository", "$CVSROOT" and "CVSROOT"?
7806 The Repository is a directory tree containing the CVS administrative
7808 work. The Repository is kept in a shared area, separate from the
7812 absolute pathname of the head of the Repository. Most command line
7816 directory at the head of the Repository".
7831 the Repository.
7862 ./CVS/Repository
7864 Repository that was used to create the working directory.
7882 added files out of the Repository.
7930 from the Repository."
7953 Repository. The current branch is either the main line of development,
7965 to the Repository. You can pull BASE up to equal HEAD by executing
8070 2. A relative path to a directory or file in the Repository.
8078 1. A name for a directory within the Repository that allows you
8090 3. A relative pathname to a directory within the Repository
8092 Repository structure in your current directory.
8100 4. A relative pathname to a single file within the Repository
8193 directory called "The Repository". Each collection of files can be
8197 "committed" back into the Repository and compared against earlier
8211 directory hierarchy, called the Repository, which is separate from the
8214 Files in the Repository are stored in a format dictated by the RCS
8222 module or directory out of the Repository and into a directory tree
8230 Repository.
8259 The shared Repository provides a rendezvous for committed sources that
8307 Though the structure of your Repository and modules file interact with
8317 entire Repository to be checked out. That's simply bad planning.
8401 Then I'd run "cvsinit" to set up a Repository and read the man page