|
Lines 251-264
Link Here
|
| 251 |
<sect2> |
251 |
<sect2> |
| 252 |
<title>Updating your ports collection for the first time</title> |
252 |
<title>Updating your ports collection for the first time</title> |
| 253 |
|
253 |
|
| 254 |
<para>Since ports are tagged <quote>.</quote> (ie -CURRENT), you can |
254 |
<para>Since ports are normally tagged <quote>.</quote> (ie -CURRENT), you can |
| 255 |
correctly <quote>sync</quote> them for the first time by adding the date |
255 |
correctly <quote>sync</quote> them for the first time by using the tag |
| 256 |
keyword (cf &man.cvsup.1; for the exact format): you should |
256 |
with which your ports were shipped. E.g., if you have installed the ports |
| 257 |
specify a date as close as possible to that of <quote>shipping</quote> of |
257 |
collection from a 5.3-RELEASE Disk, you will use |
| 258 |
your ports tree. After <command>cvsup</command> has correctly created the ports |
258 |
<programlisting>ports-all tag=RELEASE_5_3_0 list=cvs:.</programlisting> |
|
|
259 |
(which is tantamount to writing just |
| 260 |
<programlisting>ports-all tag=RELEASE_5_3_0</programlisting> |
| 261 |
and subsequently renaming the checkouts file.) |
| 262 |
After <command>cvsup</command> has correctly created the ports |
| 259 |
checkouts file, which is precisely the goal of this first |
263 |
checkouts file, which is precisely the goal of this first |
| 260 |
special sync operation, the date field must be removed; |
264 |
special sync operation, the normal <quote>.</quote> tag can be used |
| 261 |
all subsequent updates will be carried out smoothly.</para> |
265 |
and the list field must be removed; |
|
|
266 |
all subsequent updates will be carried out smoothly.</para> |
| 262 |
|
267 |
|
| 263 |
<para>If you have been reading the apparently nit-picking |
268 |
<para>If you have been reading the apparently nit-picking |
| 264 |
remarks in these sections, you will probably have recognized |
269 |
remarks in these sections, you will probably have recognized |