1 # (Be in -*- mode: python; coding: utf-8 -*- mode.)
3 # ====================================================================
4 # Copyright (c) 2006-2010 CollabNet. All rights reserved.
6 # This software is licensed as described in the file COPYING, which
7 # you should have received as part of this distribution. The terms
8 # are also available at http://subversion.tigris.org/license-1.html.
9 # If newer versions of this license are posted there, you may use a
10 # newer version instead, at your option.
12 # This software consists of voluntary contributions made by many
13 # individuals. For exact contribution history, see the revision
14 # history and logs, available at http://cvs2svn.tigris.org/.
15 # ====================================================================
17 # #####################
18 # ## PLEASE READ ME! ##
19 # #####################
21 # This is a template for an options file that can be used to configure
22 # cvs2svn to convert to git rather than to Subversion. See
23 # www/cvs2git.html and www/cvs2svn.html for general information, and
24 # see the comments in this file for information about what options are
25 # available and how they can be set.
27 # The program that is run to convert from CVS to git is called
28 # cvs2git. Run it with the --options option, passing it this file
31 # cvs2git --options=cvs2git-example.options
33 # The output of cvs2git is a blob file and a dump file that can be
34 # loaded into git using the "git fast-import" command. Please read
35 # www/cvs2git.html for more information.
37 # Many options do not have defaults, so it is easier to copy this file
38 # and modify what you need rather than creating a new options file
39 # from scratch. This file is in Python syntax, but you don't need to
40 # know Python to modify it. But if you *do* know Python, then you
41 # will be happy to know that you can use arbitary Python constructs to
42 # do fancy configuration tricks.
44 # But please be aware of the following:
46 # * In many places, leading whitespace is significant in Python (it is
47 # used instead of curly braces to group statements together).
48 # Therefore, if you don't know what you are doing, it is best to
49 # leave the whitespace as it is.
51 # * In normal strings, Python treats a backslash ("\") as an escape
52 # character. Therefore, if you want to specify a string that
53 # contains a backslash, you need either to escape the backslash with
54 # another backslash ("\\"), or use a "raw string", as in one if the
55 # following equivalent examples:
57 # cvs_executable = 'c:\\windows\\system32\\cvs.exe'
58 # cvs_executable = r'c:\windows\system32\cvs.exe'
60 # See http://docs.python.org/tutorial/introduction.html#strings for
63 # Two identifiers will have been defined before this file is executed,
64 # and can be used freely within this file:
66 # ctx -- a Ctx object (see cvs2svn_lib/context.py), which holds
67 # many configuration options
69 # run_options -- an instance of the GitRunOptions class (see
70 # cvs2svn_lib/git_run_options.py), which holds some variables
71 # governing how cvs2git is run
74 # Import some modules that are used in setting the options:
77 from cvs2svn_lib import config
78 from cvs2svn_lib import changeset_database
79 from cvs2svn_lib.common import CVSTextDecoder
80 from cvs2svn_lib.log import logger
81 from cvs2svn_lib.project import Project
82 from cvs2svn_lib.git_revision_collector import GitRevisionCollector
83 from cvs2svn_lib.external_blob_generator import ExternalBlobGenerator
84 from cvs2svn_lib.git_output_option import GitRevisionMarkWriter
85 from cvs2svn_lib.git_output_option import GitOutputOption
86 from cvs2svn_lib.dvcs_common import KeywordHandlingPropertySetter
87 from cvs2svn_lib.revision_manager import NullRevisionCollector
88 from cvs2svn_lib.rcs_revision_manager import RCSRevisionReader
89 from cvs2svn_lib.cvs_revision_manager import CVSRevisionReader
90 from cvs2svn_lib.symbol_strategy import AllBranchRule
91 from cvs2svn_lib.symbol_strategy import AllTagRule
92 from cvs2svn_lib.symbol_strategy import BranchIfCommitsRule
93 from cvs2svn_lib.symbol_strategy import ExcludeRegexpStrategyRule
94 from cvs2svn_lib.symbol_strategy import ForceBranchRegexpStrategyRule
95 from cvs2svn_lib.symbol_strategy import ForceTagRegexpStrategyRule
96 from cvs2svn_lib.symbol_strategy import ExcludeTrivialImportBranchRule
97 from cvs2svn_lib.symbol_strategy import ExcludeVendorBranchRule
98 from cvs2svn_lib.symbol_strategy import HeuristicStrategyRule
99 from cvs2svn_lib.symbol_strategy import UnambiguousUsageRule
100 from cvs2svn_lib.symbol_strategy import HeuristicPreferredParentRule
101 from cvs2svn_lib.symbol_strategy import SymbolHintsFileRule
102 from cvs2svn_lib.symbol_transform import ReplaceSubstringsSymbolTransform
103 from cvs2svn_lib.symbol_transform import RegexpSymbolTransform
104 from cvs2svn_lib.symbol_transform import IgnoreSymbolTransform
105 from cvs2svn_lib.symbol_transform import NormalizePathsSymbolTransform
106 from cvs2svn_lib.property_setters import AutoPropsPropertySetter
107 from cvs2svn_lib.property_setters import ConditionalPropertySetter
108 from cvs2svn_lib.property_setters import cvs_file_is_binary
109 from cvs2svn_lib.property_setters import CVSBinaryFileDefaultMimeTypeSetter
110 from cvs2svn_lib.property_setters import CVSBinaryFileEOLStyleSetter
111 from cvs2svn_lib.property_setters import DefaultEOLStyleSetter
112 from cvs2svn_lib.property_setters import EOLStyleFromMimeTypeSetter
113 from cvs2svn_lib.property_setters import ExecutablePropertySetter
114 from cvs2svn_lib.property_setters import KeywordsPropertySetter
115 from cvs2svn_lib.property_setters import MimeMapper
116 from cvs2svn_lib.property_setters import SVNBinaryFileKeywordsPropertySetter
118 # To choose the level of logging output, uncomment one of the
120 #logger.log_level = logger.WARN
121 #logger.log_level = logger.QUIET
122 logger.log_level = logger.NORMAL
123 #logger.log_level = logger.VERBOSE
124 #logger.log_level = logger.DEBUG
127 # The directory to use for temporary files:
128 ctx.tmpdir = r'cvs2svn-tmp'
130 # During FilterSymbolsPass, cvs2git records the contents of file
131 # revisions into a "blob" file in git-fast-import format. The
132 # ctx.revision_collector option configures that process. Choose one of the two ersions and customize its options.
134 # This first alternative is much slower but is better tested and has a
135 # chance of working with CVSNT repositories. It invokes CVS or RCS to
136 # reconstuct the contents of CVS file revisions:
137 ctx.revision_collector = GitRevisionCollector(
138 # The file in which to write the git-fast-import stream that
139 # contains the file revision contents:
140 'cvs2svn-tmp/git-blob.dat',
142 # The following option specifies how the revision contents of the
143 # RCS files should be read.
145 # RCSRevisionReader uses RCS's "co" program to extract the
146 # revision contents of the RCS files during CollectRevsPass. The
147 # constructor argument specifies how to invoke the "co"
150 # CVSRevisionReader uses the "cvs" program to extract the revision
151 # contents out of the RCS files during OutputPass. This option is
152 # considerably slower than RCSRevisionReader because "cvs" is
153 # considerably slower than "co". However, it works in some
154 # situations where RCSRevisionReader fails; see the HTML
155 # documentation of the "--use-cvs" option for details. The
156 # constructor argument specifies how to invoke the "co"
159 # Uncomment one of the two following lines:
160 #RCSRevisionReader(co_executable=r'co'),
161 CVSRevisionReader(cvs_executable=r'cvs'),
163 # This second alternative is vastly faster than the version above. It
164 # uses an external Python program to reconstruct the contents of CVS
166 #ctx.revision_collector = ExternalBlobGenerator('cvs2svn-tmp/git-blob.dat')
168 # cvs2git doesn't need a revision reader because OutputPass only
169 # refers to blobs that were output during CollectRevsPass, so leave
170 # this option set to None.
171 ctx.revision_reader = None
173 # Change the following line to True if the conversion should only
174 # include the trunk of the repository (i.e., all branches and tags
175 # should be omitted from the conversion):
176 ctx.trunk_only = False
178 # How to convert CVS author names, log messages, and filenames to
179 # Unicode. The first argument to CVSTextDecoder is a list of encoders
180 # that are tried in order in 'strict' mode until one of them succeeds.
181 # If none of those succeeds, then fallback_encoder (if it is
182 # specified) is used in lossy 'replace' mode. Setting a fallback
183 # encoder ensures that the encoder always succeeds, but it can cause
185 ctx.cvs_author_decoder = CVSTextDecoder(
191 #fallback_encoding='ascii'
193 ctx.cvs_log_decoder = CVSTextDecoder(
199 #fallback_encoding='ascii'
201 # You might want to be especially strict when converting filenames to
202 # Unicode (e.g., maybe not specify a fallback_encoding).
203 ctx.cvs_filename_decoder = CVSTextDecoder(
209 #fallback_encoding='ascii'
212 # Template for the commit message to be used for initial project
214 ctx.initial_project_commit_message = (
215 'Standard project directories initialized by cvs2svn.'
218 # Template for the commit message to be used for post commits, in
219 # which modifications to a vendor branch are copied back to trunk.
220 # This message can use '%(revnum)d' to include the SVN revision number
221 # of the revision that included the change to the vendor branch
222 # (admittedly rather pointless in a cvs2git conversion).
223 ctx.post_commit_message = (
224 'This commit was generated by cvs2svn to track changes on a CVS '
228 # Template for the commit message to be used for commits in which
229 # symbols are created. This message can use '%(symbol_type)s' to
230 # include the type of the symbol ('branch' or 'tag') or
231 # '%(symbol_name)s' to include the name of the symbol.
232 ctx.symbol_commit_message = (
233 "This commit was manufactured by cvs2svn to create %(symbol_type)s "
237 # Template for the commit message to be used for commits in which
238 # tags are pseudo-merged back to their source branch. This message can
239 # use '%(symbol_name)s' to include the name of the symbol.
240 # (Not used by default unless you enable tie_tag_fixup_branches on
242 ctx.tie_tag_ancestry_message = (
243 "This commit was manufactured by cvs2svn to tie ancestry for "
244 "tag '%(symbol_name)s' back to the source branch."
247 # Some CVS clients for MacOS store resource fork data into CVS along
248 # with the file contents itself by wrapping it all up in a container
249 # format called "AppleSingle". Subversion currently does not support
250 # MacOS resource forks. Nevertheless, sometimes the resource fork
251 # information is not necessary and can be discarded. Set the
252 # following option to True if you would like cvs2svn to identify files
253 # whose contents are encoded in AppleSingle format, and discard all
254 # but the data fork for such files before committing them to
255 # Subversion. (Please note that AppleSingle contents are identified
256 # by the AppleSingle magic number as the first four bytes of the file.
257 # This check is not failproof, so only set this option if you think
259 ctx.decode_apple_single = False
261 # This option can be set to the name of a filename to which are stored
262 # statistics and conversion decisions about the CVS symbols.
263 ctx.symbol_info_filename = None
264 #ctx.symbol_info_filename = 'symbol-info.txt'
266 # cvs2svn uses "symbol strategy rules" to help decide how to handle
267 # CVS symbols. The rules in a project's symbol_strategy_rules are
268 # applied in order, and each rule is allowed to modify the symbol.
269 # The result (after each of the rules has been applied) is used for
272 # 1. A CVS symbol might be used as a tag in one file and as a branch
273 # in another file. cvs2svn has to decide whether to convert such a
274 # symbol as a tag or as a branch. cvs2svn uses a series of
275 # heuristic rules to decide how to convert a symbol. The user can
276 # override the default rules for specific symbols or symbols
277 # matching regular expressions.
279 # 2. cvs2svn is also capable of excluding symbols from the conversion
280 # (provided no other symbols depend on them.
282 # 3. CVS does not record unambiguously the line of development from
283 # which a symbol sprouted. cvs2svn uses a heuristic to choose a
284 # symbol's "preferred parents".
286 # The standard branch/tag/exclude StrategyRules do not change a symbol
287 # that has already been processed by an earlier rule, so in effect the
288 # first matching rule is the one that is used.
290 global_symbol_strategy_rules = [
291 # It is possible to specify manually exactly how symbols should be
292 # converted and what line of development should be used as the
293 # preferred parent. To do so, create a file containing the symbol
294 # hints and enable the following option.
296 # The format of the hints file is described in the documentation
297 # for the --symbol-hints command-line option. The file output by
298 # the --write-symbol-info (i.e., ctx.symbol_info_filename) option
299 # is in the same format. The simplest way to use this option is
300 # to run the conversion through CollateSymbolsPass with
301 # --write-symbol-info option, copy the symbol info and edit it to
302 # create a hints file, then re-start the conversion at
303 # CollateSymbolsPass with this option enabled.
304 #SymbolHintsFileRule('symbol-hints.txt'),
306 # To force all symbols matching a regular expression to be
307 # converted as branches, add rules like the following:
308 #ForceBranchRegexpStrategyRule(r'branch.*'),
310 # To force all symbols matching a regular expression to be
311 # converted as tags, add rules like the following:
312 #ForceTagRegexpStrategyRule(r'tag.*'),
314 # To force all symbols matching a regular expression to be
315 # excluded from the conversion, add rules like the following:
316 #ExcludeRegexpStrategyRule(r'unknown-.*'),
318 # Sometimes people use "cvs import" to get their own source code
319 # into CVS. This practice creates a vendor branch 1.1.1 and
320 # imports the code onto the vendor branch as 1.1.1.1, then copies
321 # the same content to the trunk as version 1.1. Normally, such
322 # vendor branches are useless and they complicate the SVN history
323 # unnecessarily. The following rule excludes any branches that
324 # only existed as a vendor branch with a single import (leaving
325 # only the 1.1 revision). If you want to retain such branches,
326 # comment out the following line. (Please note that this rule
327 # does not exclude vendor *tags*, as they are not so easy to
329 ExcludeTrivialImportBranchRule(),
331 # To exclude all vendor branches (branches that had "cvs import"s
332 # on them but no other kinds of commits), uncomment the following
334 #ExcludeVendorBranchRule(),
336 # Usually you want this rule, to convert unambiguous symbols
337 # (symbols that were only ever used as tags or only ever used as
338 # branches in CVS) the same way they were used in CVS:
339 UnambiguousUsageRule(),
341 # If there was ever a commit on a symbol, then it cannot be
342 # converted as a tag. This rule causes all such symbols to be
343 # converted as branches. If you would like to resolve such
344 # ambiguities manually, comment out the following line:
345 BranchIfCommitsRule(),
347 # Last in the list can be a catch-all rule that is used for
348 # symbols that were not matched by any of the more specific rules
349 # above. (Assuming that BranchIfCommitsRule() was included above,
350 # then the symbols that are still indeterminate at this point can
351 # sensibly be converted as branches or tags.) Include at most one
352 # of these lines. If none of these catch-all rules are included,
353 # then the presence of any ambiguous symbols (that haven't been
354 # disambiguated above) is an error:
356 # Convert ambiguous symbols based on whether they were used more
357 # often as branches or as tags:
358 HeuristicStrategyRule(),
359 # Convert all ambiguous symbols as branches:
361 # Convert all ambiguous symbols as tags:
364 # The last rule is here to choose the preferred parent of branches
365 # and tags, that is, the line of development from which the symbol
367 HeuristicPreferredParentRule(),
370 # Specify a username to be used for commits for which CVS doesn't
371 # record the original author (for example, the creation of a branch).
372 # This should be a simple (unix-style) username, but it can be
373 # translated into a git-style name by the author_transforms map.
374 ctx.username = 'cvs2svn'
376 # ctx.file_property_setters and ctx.revision_property_setters contain
377 # rules used to set the svn properties on files in the converted
378 # archive. For each file, the rules are tried one by one. Any rule
379 # can add or suppress one or more svn properties. Typically the rules
380 # will not overwrite properties set by a previous rule (though they
381 # are free to do so). ctx.file_property_setters should be used for
382 # properties that remain the same for the life of the file; these
383 # should implement FilePropertySetter. ctx.revision_property_setters
384 # should be used for properties that are allowed to vary from revision
385 # to revision; these should implement RevisionPropertySetter.
387 # Obviously, SVN properties per se are not interesting for a cvs2git
388 # conversion, but some of these properties have side-effects that do
389 # affect the git output. FIXME: Document this in more detail.
390 ctx.file_property_setters.extend([
391 # To read auto-props rules from a file, uncomment the following line
392 # and specify a filename. The boolean argument specifies whether
393 # case should be ignored when matching filenames to the filename
394 # patterns found in the auto-props file:
395 #AutoPropsPropertySetter(
396 # r'/home/username/.subversion/config',
400 # To read mime types from a file and use them to set svn:mime-type
401 # based on the filename extensions, uncomment the following line
402 # and specify a filename (see
403 # http://en.wikipedia.org/wiki/Mime.types for information about
405 #MimeMapper(r'/etc/mime.types', ignore_case=False),
407 # Omit the svn:eol-style property from any files that are listed
408 # as binary (i.e., mode '-kb') in CVS:
409 CVSBinaryFileEOLStyleSetter(),
411 # If the file is binary and its svn:mime-type property is not yet
412 # set, set svn:mime-type to 'application/octet-stream'.
413 CVSBinaryFileDefaultMimeTypeSetter(),
415 # To try to determine the eol-style from the mime type, uncomment
416 # the following line:
417 #EOLStyleFromMimeTypeSetter(),
419 # Choose one of the following lines to set the default
420 # svn:eol-style if none of the above rules applied. The argument
421 # is the svn:eol-style that should be applied, or None if no
422 # svn:eol-style should be set (i.e., the file should be treated as
425 # The default is to treat all files as binary unless one of the
426 # previous rules has determined otherwise, because this is the
427 # safest approach. However, if you have been diligent about
428 # marking binary files with -kb in CVS and/or you have used the
429 # above rules to definitely mark binary files as binary, then you
430 # might prefer to use 'native' as the default, as it is usually
431 # the most convenient setting for text files. Other possible
432 # options: 'CRLF', 'CR', 'LF'.
433 DefaultEOLStyleSetter(None),
434 #DefaultEOLStyleSetter('native'),
436 # Prevent svn:keywords from being set on files that have
437 # svn:eol-style unset.
438 SVNBinaryFileKeywordsPropertySetter(),
440 # If svn:keywords has not been set yet, set it based on the file's
442 KeywordsPropertySetter(config.SVN_KEYWORDS_VALUE),
444 # Set the svn:executable flag on any files that are marked in CVS as
446 ExecutablePropertySetter(),
448 # The following causes keywords to be untouched in binary files and
449 # collapsed in all text to be committed:
450 ConditionalPropertySetter(
451 cvs_file_is_binary, KeywordHandlingPropertySetter('untouched'),
453 KeywordHandlingPropertySetter('collapsed'),
456 ctx.revision_property_setters.extend([
459 # To skip the cleanup of temporary files, uncomment the following
461 #ctx.skip_cleanup = True
464 # In CVS, it is perfectly possible to make a single commit that
465 # affects more than one project or more than one branch of a single
466 # project. Subversion also allows such commits. Therefore, by
467 # default, when cvs2svn sees what looks like a cross-project or
468 # cross-branch CVS commit, it converts it into a
469 # cross-project/cross-branch Subversion commit.
471 # However, other tools and SCMs have trouble representing
472 # cross-project or cross-branch commits. (For example, Trac's Revtree
473 # plugin, http://www.trac-hacks.org/wiki/RevtreePlugin is confused by
474 # such commits.) Therefore, we provide the following two options to
475 # allow cross-project/cross-branch commits to be suppressed.
477 # cvs2git only supports single-project conversions (multiple-project
478 # conversions wouldn't really make sense for git anyway). So this
479 # option must be set to False:
480 ctx.cross_project_commits = False
482 # git itself doesn't allow commits that affect more than one branch,
483 # so this option must be set to False:
484 ctx.cross_branch_commits = False
486 # cvs2git does not yet handle translating .cvsignore files into
487 # .gitignore files, so by default, the .cvsignore files are included
488 # in the conversion output. If you would like to omit the .cvsignore
489 # files from the output, set this option to False:
490 ctx.keep_cvsignore = True
492 # By default, it is a fatal error for a CVS ",v" file to appear both
493 # inside and outside of an "Attic" subdirectory (this should never
494 # happen, but frequently occurs due to botched repository
495 # administration). If you would like to retain both versions of such
496 # files, change the following option to True, and the attic version of
497 # the file will be written to a subdirectory called "Attic" in the
499 ctx.retain_conflicting_attic_files = False
501 # CVS uses unix login names as author names whereas git requires
502 # author names to be of the form "foo <bar>". The default is to set
503 # the git author to "cvsauthor <cvsauthor>". author_transforms can be
504 # used to map cvsauthor names (e.g., "jrandom") to a true name and
505 # email address (e.g., "J. Random <jrandom@example.com>" for the
506 # example shown). All strings should be either Unicode strings (i.e.,
507 # with "u" as a prefix) or 8-bit strings in the utf-8 encoding. The
508 # values can either be strings in the form "name <email>" or tuples
509 # (name, email). Please substitute your own project's usernames here
510 # to use with the author_transforms option of GitOutputOption below.
512 'jrandom' : ('J. Random', 'jrandom@example.com'),
513 'mhagger' : 'Michael Haggerty <mhagger@alum.mit.edu>',
514 'brane' : (u'Branko Čibej', 'brane@xbc.nu'),
515 'ringstrom' : 'Tobias Ringström <tobias@ringstrom.mine.nu>',
516 'dionisos' : (u'Erik Hülsmann', 'e.huelsmann@gmx.net'),
518 # This one will be used for commits for which CVS doesn't record
519 # the original author, as explained above.
520 'cvs2svn' : 'cvs2svn <admin@example.com>',
523 # This is the main option that causes cvs2svn to output to a
524 # "fastimport"-format dumpfile rather than to Subversion:
525 ctx.output_option = GitOutputOption(
526 # The file in which to write the git-fast-import stream that
527 # contains the changesets and branch/tag information:
528 os.path.join(ctx.tmpdir, 'git-dump.dat'),
530 # The blobs will be written via the revision recorder, so in
531 # OutputPass we only have to emit references to the blob marks:
532 GitRevisionMarkWriter(),
534 # Optional map from CVS author names to git author names:
535 author_transforms=author_transforms,
538 # Change this option to True to turn on profiling of cvs2svn (for
539 # debugging purposes):
540 run_options.profiling = False
543 # Should CVSItem -> Changeset database files be memory mapped? In
544 # some tests, using memory mapping speeded up the overall conversion
545 # by about 5%. But this option can cause the conversion to fail with
546 # an out of memory error if the conversion computer runs out of
547 # virtual address space (e.g., when running a very large conversion on
548 # a 32-bit operating system). Therefore it is disabled by default.
549 # Uncomment the following line to allow these database files to be
551 #changeset_database.use_mmap_for_cvs_item_to_changeset_table = True
553 # Now set the project to be converted to git. cvs2git only supports
554 # single-project conversions, so this method must only be called
556 run_options.set_project(
557 # The filesystem path to the part of the CVS repository (*not* a
558 # CVS working copy) that should be converted. This may be a
559 # subdirectory (i.e., a module) within a larger CVS repository.
560 r'test-data/main-cvsrepos',
562 # A list of symbol transformations that can be used to rename
563 # symbols in this project.
565 # Use IgnoreSymbolTransforms like the following to completely
566 # ignore symbols matching a regular expression when parsing
567 # the CVS repository, for example to avoid warnings about
568 # branches with two names and to choose the preferred name.
569 # It is *not* recommended to use this instead of
570 # ExcludeRegexpStrategyRule; though more efficient,
571 # IgnoreSymbolTransforms are less flexible and don't exclude
572 # branches correctly. The argument is a Python-style regular
573 # expression that has to match the *whole* CVS symbol name:
574 #IgnoreSymbolTransform(r'nightly-build-tag-.*')
576 # RegexpSymbolTransforms transform symbols textually using a
577 # regular expression. The first argument is a Python regular
578 # expression pattern and the second is a replacement pattern.
579 # The pattern is matched against each symbol name. If it
580 # matches the whole symbol name, then the symbol name is
581 # replaced with the corresponding replacement text. The
582 # replacement can include substitution patterns (e.g., r'\1'
583 # or r'\g<name>'). Typically you will want to use raw strings
584 # (strings with a preceding 'r', like shown in the examples)
585 # for the regexp and its replacement to avoid backslash
586 # substitution within those strings.
587 #RegexpSymbolTransform(r'release-(\d+)_(\d+)',
589 #RegexpSymbolTransform(r'release-(\d+)_(\d+)_(\d+)',
590 # r'release-\1.\2.\3'),
592 # Simple 1:1 character replacements can also be done. The
593 # following transform, which converts backslashes into forward
594 # slashes, should usually be included:
595 ReplaceSubstringsSymbolTransform('\\','/'),
597 # This last rule eliminates leading, trailing, and repeated
598 # slashes within the output symbol names:
599 NormalizePathsSymbolTransform(),
602 # See the definition of global_symbol_strategy_rules above for a
603 # description of this option:
604 symbol_strategy_rules=global_symbol_strategy_rules,