Issue 259 - Update build documentation to include cvs update -A
Summary: Update build documentation to include cvs update -A
Status: CLOSED FIXED
Alias: None
Product: Build Tools
Classification: Code
Component: documentation (show other issues)
Version: 609
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-12-27 12:45 UTC by issues@www
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description issues@www 2000-12-27 12:45:16 UTC 
The build documentation focuses on getting a particular release of the software
and stayiong there.  It does not mention to keep current with the main trunk you
might need to enter the command 'cvs update -A' to break the tag for '609' for
example.

I have been updating regularly and not understanding why I am not getting any
updates.  Now that I have an unrestricted update this should occur regularly.

This hint would assist others who might be having problems.
Comment 1 Unknown 2001-01-30 09:29:14 UTC 
Isn't it possible to update using tags? For instance, you 
have the version tagged OpenOffice613 as your working copy, 
and you update to OpenOffice614 via

cvs update -rOpenOffice614

btw: I have updated the build manual.
Comment 2 Unknown 2001-04-06 14:22:56 UTC 
The build docs have been updated meanwhile. No more feedback afterwards, 
so I will close this issue.
Comment 3 chris 2002-11-07 14:36:20 UTC 
This was only an issue when using tags - we're working on branches now
anyway.  Oh, and Ken has had lots of practice with CVS now :)

Verified and closed.