From ee778d6eea54935fd05022e0ba8c49456003381a Mon Sep 17 00:00:00 2001 From: Florian Merz Date: Thu, 11 Feb 2021 14:48:24 +0100 Subject: unslug ko: move --- .../developer_guide/source_code/cvs/index.html | 136 +++++++++++++++++++++ 1 file changed, 136 insertions(+) create mode 100644 files/ko/mozilla/developer_guide/source_code/cvs/index.html (limited to 'files/ko/mozilla/developer_guide/source_code/cvs/index.html') diff --git a/files/ko/mozilla/developer_guide/source_code/cvs/index.html b/files/ko/mozilla/developer_guide/source_code/cvs/index.html new file mode 100644 index 0000000000..bcd46453fc --- /dev/null +++ b/files/ko/mozilla/developer_guide/source_code/cvs/index.html @@ -0,0 +1,136 @@ +--- +title: Mozilla Source Code Via CVS +slug: Mozilla_Source_Code_Via_CVS +--- +

Those doing active development can check out the latest source using CVS. This is the preferred method if you plan to provide patches and fix bugs, as it lets you get up-to-the-minute changes and merge them with your own.

+

If you want to compile a product for release, it is generally better to Download Mozilla Source Code tarballs.

+

Quick Start Guide

+

I seem to not be editing this page in what others on this development site deem appropriate. So, if you are going to just remove this section, can you please be so kind as to suggest an alternate title of a new page that I can put this information on? Thanks, Jeff Carr

+

The basic steps to checkout the trunk (unstable) Firefox sources are:

+
cvs -d :pserver:anonymous:anonymous@cvs-mirror.mozilla.org:/cvsroot co mozilla/client.mk
+cd mozilla
+make -f client.mk checkout MOZ_CO_PROJECT=browser
+
+

Note that on Windows, your source tree must be located at a /cygdrive/<c> mount point. It must not be located within your /home.

+

Getting Started

+

CVS means "Concurrent Versioning System". To learn more about CVS in general, visit ximbiot.com, or read the tutorial.

+

Anyone can check out (also known as "pull" or "download") the sources via CVS, but only certain people have the ability to check in (make changes, also known as "commit"). Those people are the module owners and their delegates. Read our document on hacking mozilla to find out how to get the ability to check in. You may also wish to read about using SSH to connect to CVS.

+

Requirements

+

To check out the sources, you need to be running CVS 1.11 or later. 1.12.13 does not work with the CVS server, and instead results in hangs, although 1.12.9 is known to work. Furthermore, you must use GNU make to check out and build Mozilla. No other "make" program is acceptable. On windows, mac and regular GNU systems (like GNU/Linux), use "make" to run GNU make; on most non-GNU unixes (like e.g. Solaris, etc.), use "gmake".

+

CVS Client Settings

+

The "cvsroot" (repository identification string) used for anonymous access to Mozilla CVS is

+
:pserver:anonymous:anonymous@cvs-mirror.mozilla.org:/cvsroot
+
+

If you are using a graphical CVS interface, use the following server data:

+ +

Selecting a Project to Pull

+

Since several different applications are built from the same basic source code, you must choose which application to checkout on the command line using the MOZ_CO_PROJECT variable. This information has to be supplied when it comes to the checkout of the actual source code (see the appropriate checkout section below, according to the branch you want to checkout). The possible options include the following:

+
+
+ browser 
+
+ The standalone "Firefox" browser.
+
+ mail 
+
+ The standalone "Thunderbird" mail/news client.
+
+ suite 
+
+ The traditional "Mozilla" SeaMonkey suite of browser, mail/news, composer, and other applications.
+
+ minimo 
+
+ The standalone browser for small devices.
+
+ composer 
+
+ The standalone HTML composer.
+
+ calendar 
+
+ The standalone "Sunbird" calendar app.
+
+ xulrunner 
+
+ The next-generation XUL application launcher.
+
+ macbrowser 
+
+ The "Camino" native browser for Macintosh.
+
+ all 
+
+ Check out sources for all of the above projects, plus some additional utility code
+
+

Multiple projects can be specified with commas: MOZ_CO_PROJECT=suite,browser,xulrunner.

+

Note that if you are using a custom <tt>.mozconfig</tt> file, you can also specify MOZ_CO_PROJECT there, instead of including it on the command line.

+

Checking Out a New Source Tree

+

Check Tinderbox

+

Before pulling a tree, you should always check the appropriate Tinderbox to make sure that the codebase is not broken. If there are red tinderboxes, it is usually advisable to wait until they are green before pulling a tree.

+

Branch HEAD

+

To check out a new source tree from scratch, get the <tt>client.mk</tt> file which contains makefile instructions which are used to pull the rest of the tree:

+
$ cvs -d :pserver:anonymous:anonymous@cvs-mirror.mozilla.org:/cvsroot co mozilla/client.mk
+
+

Note: if you have already set up a <tt>.mozconfig</tt> file, you may also need to check out the following files:

+
+
+ Firefox 
+
+ 
cvs -d :pserver:anonymous:anonymous@cvs-mirror.mozilla.org:/cvsroot co mozilla/browser/config/mozconfig
+
+
+ Thunderbird 
+
+ 
cvs -d :pserver:anonymous:anonymous@cvs-mirror.mozilla.org:/cvsroot co mozilla/mail/config/mozconfig
+
+
+

Specific Branch

+

If you want to check out the source code of a specific CVS branch, use

+
$ cvs -d :pserver:anonymous:anonymous@cvs-mirror.mozilla.org:/cvsroot co -r BRANCH mozilla/client.mk
+
+

instead. To, for example, pull the Firefox 2.0 development branch, replace BRANCH above with MOZILLA_1_8_BRANCH. For available branch tags in Mozilla, see CVS Tags.

+

The information on pulling project specific .mozconfig files as listed in the previous section apply to other branches than HEAD as well of course.

+

Checkout

+

After having chosen the correct branch, run:

+
$ cd mozilla
+$ make -f client.mk checkout MOZ_CO_PROJECT=option,option
+
+

As mentioned above, if you are using a custom .mozconfig file where you have already specified the MOZ_CO_PROJECT variable, you do not need to repeat it here on command line.

+
+ Always use <tt>client.mk</tt> to checkout the Mozilla sources: do not check out the <tt>mozilla/</tt> module directly. Various subprojects such as NSS, NSPR, and LDAP C SDK are pulled from stable release tags, even when regular mozilla development occurs on the trunk.
+

Updating a Source Tree

+

Branch HEAD

+

In order to update a source tree (be it branch HEAD or a specific branch) to latest branch HEAD, run:

+
$ cd mozilla
+$ cvs up -A client.mk
+
+

The -A option removes any "sticky branch" information, which leads to the effect that the tree is updated to HEAD.

+

Specific Branch

+

To update a source tree which was pulled from a specific branch, use

+
$ cd mozilla
+$ cvs up -r BRANCH client.mk
+
+

instead. Replace BRANCH by the tag of the branch you want to update.

+

Checkout

+

Having updated client.mk, you can do the checkout:

+
$ make -f client.mk checkout MOZ_CO_PROJECT=option,option
+
+

As always, if you use a custom .mozconfig file where MOZ_CO_PROJECT is already defined, you do not need to repeat it on command line.

+

Creating a Diff File

+

In order to create a diff of a single local file against the current file in the repository, use:

+
$ cvs diff -u8p FILENAME
+
+

See Creating a patch for more information.

+

Converting a Downloaded Source Tree

+

Downloaded source trees from mozilla.org (source tarballs) are already set up with CVS information, like a normal checkout. You can update these trees like normal trees to the latest code, without special action. See previous section on how to update a source tree.

+


+ interwiki link

+

{{ languages( { "fr": "fr/Obtenir_le_code_source_de_Mozilla_via_CVS", "ja": "ja/Mozilla_Source_Code_Via_CVS", "zh-cn": "cn/\u901a\u8fc7CVS\u83b7\u53d6\u6e90\u7801" } ) }}

-- cgit v1.2.3-54-g00ecf