1 message in com.perforce.revml[revml] Win32 changes merged in; reva...| From | Sent On | Attachments |
|---|---|---|
| Barrie Slaymaker | 24 Jan 2002 12:44 |
| Subject: | [revml] Win32 changes merged in; revamed help; more docs (optionally in html)![]() |
|---|---|
| From: | Barrie Slaymaker (barr...@slaysys.com) |
| Date: | 01/24/2002 12:44:27 PM |
| List: | com.perforce.revml |
The full change log (since 0.25) is below. The highlights are:
vcp's help system is now almost fully featured, and is modelled after Perforce's p4 command:
$ vcp help vcp - Version Copy, a tool for copying versions file repositories
help topics (use "vcp help <topic>" to see):
vcp General help for the vcp command
source::p4 Extracting from a p4 repository dest::p4 Inserting in to a p4 repository source::cvs Extracting from a cvs repository dest::cvs Inserting in to a cvs repository
newlines Newline, ^Z and NULL issues process How vcp works
license Copyright and license information maintenance VCP Code maintenance, debugging tips & tricks
If you're planning on hacking the source (hi, Sean :), the "maintenance" topic should be somewhat helpful. These topics are also all available through man on Unix and perldoc on any system, for instance `perldoc VCP::Maintenance` should show almost the same thing as `vcp help maintenance` does, albeit with bold and underlining and in a pager where possible.
Also, vcp can create an HTML documentation directory like so:
$ bin/vcp html Generating HTML in /home/barries/src/VCP/vcp_html/...................... Finished, index file is /home/barries/src/VCP/vcp_html/index.html
that I have online at:
http://slaysys.com:81/src/revengine/vcp_html/
For instance, the maintenance topic listed above is at:
http://slaysys.com:81/src/revengine/vcp_html/VCP/Maintenance.html
Hopefully this will go a long way towards making the docs more accessible and usable. We should probably find a long term home for them, whether in the public depot or somewhere else (I like the public depot idea, let me know if that's "good enough").
Also checked in are the Win32 changes, which cause the tests t/90cvs.t and t/90p4.t to exit oddly after running sucessfuly; I suspect they're leaking a bogus return value after killing off the p4d daemon they start.
Anyway, please feel free to test the help system out and comment on the docs.
Thanks,
Barrie
CHANGES for vcp - Version CoPy
- Win32 fixes to - gentrevml - VCP::TestUtils (these break the Unix test suite in a really minor way; the t/90p4.t and t/90cvs.t test scripts exit with a non-zero result code; need to fix that) - VCP::*::cvs, VCP::*::p4. - added "vcp html" to allow html documentation to be built. - Rewrote 'vcp help' so it has a p4-like index and can get at all of the module documentation (though internal-only stuff is not listed in the index, it can be reached). - VCP::Source::cvs: ignore waiting for and obtained lock messages. Suggested by Thomas Quinot <qui...@inf.enst.fr> - Added the VCPNODELETE option - VCP::Patch now closes it's patch file (this matters on Win32). - Added hexdump.pl, quite useful for looking in to problems involving lineends, embedded ^Z, and embedded NULL (\000) chars. - Added lib/VCP/License.pod - Added lib/VCP/Maintenance.pod - Added lib/VCP/Newlines.pod - Added lib/VCP/Process.pod - Rewrote vcp's POD - cleaned up various other POD - Simplified the <source> and <dest> parsing; we no longer allow a ' ' after the ':' in the scheme:foo syntax. - vcp will no longer die if it can't delete a working file. - VCP::Plugin now has an extra call to cwd() to get p4 to act right; this needs to be cleaned up a bit by directly setting the environment (I think) - the test suite now skips all cvs-related tests if it can't find cvs. - Require Regexp::Shellish 0.93 so that --bootstrap can accept the "..." wildcard and be consistent with other wildcards. - Updated copyrights in many POD files.
0.26 Tue Dec 18 05:21:09 EST 2001 - switched to use Text::Diff, no more Unix diff dependency. Added VCP::DiffFormat. - Added VCP:Patch. No more unix patch dependency




