Source string Read only

(itstool) path: step/para
153/1530
Context English State
Note that you will need to add any files that were added since the last vendor import, and remove any that were removed. To facilitate this, you should prepare sorted lists of the contents of the vendor tree and of the sources you are about to import:
<prompt>%</prompt> <userinput>cd vendor/<replaceable>foo</replaceable>/dist</userinput>
<prompt>%</prompt> <userinput>svn list -R | grep -v '/$' | sort &gt; ../<replaceable>old</replaceable></userinput>
<prompt>%</prompt> <userinput>cd ../<replaceable>foo-9.9</replaceable></userinput>
<prompt>%</prompt> <userinput>find . -type f | cut -c 3- | sort &gt; ../<replaceable>new</replaceable></userinput>
With these two files, the following command will list removed files (files only in <filename><replaceable>old</replaceable></filename>):
<prompt>%</prompt> <userinput>comm -23 ../<replaceable>old</replaceable> ../<replaceable>new</replaceable></userinput>
While the command below will list added files (files only in <filename><replaceable>new</replaceable></filename>):
<prompt>%</prompt> <userinput>comm -13 ../<replaceable>old</replaceable> ../<replaceable>new</replaceable></userinput>
Let us put this together:
<prompt>%</prompt> <userinput>cd vendor/<replaceable>foo</replaceable>/<replaceable>foo-9.9</replaceable></userinput>
<prompt>%</prompt> <userinput>tar cf - . | tar xf - -C ../dist</userinput>
<prompt>%</prompt> <userinput>cd ../dist</userinput>
<prompt>%</prompt> <userinput>comm -23 ../<replaceable>old</replaceable> ../<replaceable>new</replaceable> | xargs svn remove</userinput>
<prompt>%</prompt> <userinput>comm -13 ../<replaceable>old</replaceable> ../<replaceable>new</replaceable> | xargs svn add</userinput>
If there are new directories in the new distribution, the last command will fail. You will have to add the directories, and run it again. Conversely, if any directories were removed, you will have to remove them manually.
Check properties on any new files:
All text files should have <literal>svn:eol-style</literal> set to <literal>native</literal>.
All binary files should have <literal>svn:mime-type</literal> set to <literal>application/octet-stream</literal>, unless there is a more appropriate media type.
Executable files should have <literal>svn:executable</literal> set to <literal>*</literal>.
There should be no other properties on any file in the tree.
You are ready to commit, but you should first check the output of <command>svn stat</command> and <command>svn diff</command> to make sure everything is in order.
Once you have committed the new vendor release, you should tag it for future reference. The best and quickest way is to do it directly in the repository:
<prompt>%</prompt> <userinput>svn copy ^/vendor/<replaceable>foo</replaceable>/dist <replaceable>svn_base</replaceable>/vendor/<replaceable>foo</replaceable>/<replaceable>9.9</replaceable></userinput>
To get the new tag, you can update your working copy of <filename>vendor/<replaceable>foo</replaceable></filename>.
If you choose to do the copy in the checkout instead, do not forget to remove the generated <literal>svn:mergeinfo</literal> as described above.
Merging to <emphasis>-HEAD</emphasis>
After you have prepared your import, it is time to merge. Option <option>--accept=postpone</option> tells <acronym>SVN</acronym> not to handle merge conflicts yet, because they will be taken care of manually:
<prompt>%</prompt> <userinput>cd head/contrib/<replaceable>foo</replaceable></userinput>
<prompt>%</prompt> <userinput>svn update</userinput>
<prompt>%</prompt> <userinput>svn merge --accept=postpone ^/vendor/<replaceable>foo</replaceable>/dist</userinput>
Resolve any conflicts, and make sure that any files that were added or removed in the vendor tree have been properly added or removed in the main tree. It is always a good idea to check differences against the vendor branch:
<prompt>%</prompt> <userinput>svn diff --no-diff-deleted --old=^/vendor/<replaceable>foo</replaceable>/dist --new=.</userinput>
<option>--no-diff-deleted</option> tells <acronym>SVN</acronym> not to check files that are in the vendor tree but not in the main tree.
With <acronym>SVN</acronym>, there is no concept of on or off the vendor branch. If a file that previously had local modifications no longer does, just remove any left-over cruft, such as FreeBSD version tags, so it no longer shows up in diffs against the vendor tree.
If any changes are required for the world to build with the new sources, make them now — and test until you are satisfied that everything build and runs correctly.
Commit
Now, you are ready to commit. Make sure you get everything in one go. Ideally, you would have done all steps in a clean tree, in which case you can just commit from the top of that tree. That is the best way to avoid surprises. If you do it properly, the tree will move atomically from a consistent state with the old code to a consistent state with the new code.
Encumbered Files
It might occasionally be necessary to include an encumbered file in the FreeBSD source tree. For example, if a device requires a small piece of binary code to be loaded to it before the device will operate, and we do not have the source to that code, then the binary file is said to be encumbered. The following policies apply to including encumbered files in the FreeBSD source tree.

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: step/para
Flags
read-only
Source string location
book.translate.xml:4101
String age
a year ago
Source string age
a year ago
Translation file
books/developers-handbook.pot, string 684