- 12CCA3D90B11AD346B6224E009E263BE37361B8EB80E523C3B3F694586AB4E057B07B191ECDABAF4F73DB778F1C23D7FC78241F48D1CB5E1DE566A7F1BEECBB0+ 37EF9B4DA1F2D0D09343DAC421FC3D4497F210EA669F602ED6D73539F3DF3B62DC3F68D8B12BA28F1BED130FBE2E3DA3227A29669A55E1F131A08C830C58DBE6v/v_users_manual.txt(1 . 7)(1 . 7)
283 ..::[ The Bitcoin Foundation: V Users Manual ]::..
284
285
286 Doc Version: 99994 K
287 Doc Version: 99993 K
288 Author: mod6
289 Fingerprint: 0x027A8D7C0FB8A16643720F40721705A8B71EADAF
290
(44 . 16)(44 . 14)
292 Graph::Easy perl library can be installed.
293
294 Ubuntu:
295
296 apt-get install cpanminus
297 cpanm -i Graph::Easy
298
299 Gentoo [x86-64]:
300
301 emerge g-cpan
302
303 [ NOTE: Copy the next nine lines exacty as they are presented here and ]
304 [ then paste them into the shell. ]
305 [ NOTE: Copy the next nine lines exactly as they are presented here and ]
306 [ then paste them into the shell. ]
307
308 cat <<EOF > /etc/portage/package.accept_keywords
309 # required by perl-gcpan/JSON-MaybeXS-1.003005::x-g-cpan
(89 . 6)(87 . 33)
311 Gentoo:
312 emerge wget
313
314 [ Additional UNIX Commands Required ]:
315
316 Recent distributions of Linux seem ship without tools that one would
317 automatically imagine are included by default. Unfortunate users have
318 found this out the hard way. You will need the following binaries
319 on your system, or V will not run. If V does not find one of these
320 binaries on your system, it will report which one it can not find and exit.
321
322 They are, as follows (instructions on `gpg` and `wget are posted above):
323
324 gpg [GnuPG]
325 wget
326 cat
327 echo
328 ls
329 mkdir
330 patch
331 pwd
332 rm
333 sha512sum
334 sort
335 which
336 mktmp
337
338 If you do not have one of these binaries on your system, for whatever
339 reason, consult your OS documentation to determine how to install it.
340
341 [ Install GraphViz ]:
342
343 In addition to Graph::Easy, if you wish to have V automatically build the
(103 . 12)(128 . 18)
345 etc-update [ enter -5 when prompted ]
346 emerge -a graphviz [ Answer Yes at prompt ]
347
348 NOTE: Some people have had issue with getting a proper graphviz installed,
349 and subsequently no `dot` binary on their system. It may be resolved by
350 doing the following:
351
352 emerge media-gfx/graphviz
353
354 [ Download V Archive ]:
355
356 Now you must obtain the V archive & signature from:
357
358 http://thebitcoin.foundation/v/V-20170317.tar.gz
359 http://thebitcoin.foundation/v/V-20170317.tar.gz.mod6.sig
360 http://thebitcoin.foundation/v/V-20180222.tar.gz
361 http://thebitcoin.foundation/v/V-20180222.tar.gz.mod6.sig
362
363 Then check the PGP signatures supplied:
364
(117 . 11)(148 . 11)
366
367 [ Key Fingerprint: 0x027A8D7C0FB8A16643720F40721705A8B71EADAF ]
368
369 gpg --verify V-20170317.tar.gz.mod6.sig V-20170317.tar.gz
370 gpg --verify V-20180222.tar.gz.mod6.sig V-20180222.tar.gz
371
372 Then unpack the archive:
373
374 tar -xf V-20170317.tar.gz
375 tar -xf V-20180222.tar.gz
376
377 [ Start V for the first time ]:
378
(155 . 7)(186 . 7)
380 0x01]: V Usage
381
382 At this point the user has installed all of V's requirements, performed a
383 lookup of available signed mirrors, and sync'd the WoT, Patches and Seals.
384 look up of available signed mirrors, and sync'd the WoT, Patches and Seals.
385
386 What follows are usages and definitions of V's options with examples.
387
(171 . 7)(202 . 7)
389 The m or mirrors command is available to connect to the main V site:
390 http://thebitcoin.foundation Here, V can connect and pull the list of
391 available mirrors, signed by mirror administrators with L1 trust with
392 assbot and are in good standing in the WoT. Ask mod6 about this if you
393 deedbot and are in good standing in the WoT. Ask mod6 about this if you
394 want to run an authorized, signed mirror of V.
395
396 The mirrors command takes one required argument, an output directory for the
(194 . 7)(225 . 7)
398 directory) and Seals (.seals in the current working directory) directories
399 by not setting the two <pdir> or <sdir> options -- only passing a mirror URL
400 argument to the init command. If the user wishes to use their own named
401 directories, simply pass in those arguements in the exact order specified.
402 directories, simply pass in those arguments in the exact order specified.
403
404 Example:
405 ./v.pl i http://thebitcoin.foundation
(257 . 11)(288 . 11)
407 Options:
408 [ finger ]
409
410 The w or wot command will build a list of WoT entities eligable for
411 The w or wot command will build a list of WoT entities eligible for
412 creating seals for approved vpatches. If a specific vpatch has not
413 been signed by a WoT entity, it is considered a 'WILD' vpatch, and will be
414 ignored. A vpatch must be signed by both Co-Chairs of The Bitcoin Foundation
415 to be considered approved for release.
416 ignored. A vpatch must be signed by both Co-Chairs of The Bitcoin Foundation
417 to be considered approved for release.
418
419 Example:
420 ./v.pl w
(269 . 7)(300 . 6)
422 ben_vulpes:4F7907942CA8B89B01E25A762AFA1A9FD2D031DA:Ben Vulpes <benkay@gmail.com>
423 mircea_popescu:6160E1CAC8A3C52966FD76998A736F0E2FB7B452:Mircea Popescu (Acest articol are apriori avantajul aliteralitatii alaturi.) <office@polimedia.us>
424 mod6:027A8D7C0FB8A16643720F40721705A8B71EADAF:mod6 (mod6) <modsix@gmail.com>
425 punkman:F28E0095843B91CB22E7D65533588BE08B232B13:punkman
426 trinque:FC66C0C5D98C42A1D4A98B6B42F9985AFAB953C4:Michael Trinque <mike@trinque.org>
427
428 ./v.pl w finger
(277 . 7)(307 . 6)
430 ben_vulpes-2AFA1A9FD2D031DA:4F7907942CA8B89B01E25A762AFA1A9FD2D031DA:Ben Vulpes <benkay@gmail.com>
431 mircea_popescu-8A736F0E2FB7B452:6160E1CAC8A3C52966FD76998A736F0E2FB7B452:Mircea Popescu (Acest articol are apriori avantajul aliteralitatii alaturi.) <office@polimedia.us>
432 mod6-721705A8B71EADAF:027A8D7C0FB8A16643720F40721705A8B71EADAF:mod6 (mod6) <modsix@gmail.com>
433 punkman-33588BE08B232B13:F28E0095843B91CB22E7D65533588BE08B232B13:punkman
434 trinque-42F9985AFAB953C4:FC66C0C5D98C42A1D4A98B6B42F9985AFAB953C4:Michael Trinque <mike@trinque.org>
435
436 [ r | roots ]:
(298 . 8)(327 . 8)
438 [ l | leafs ]:
439
440 The l or leafs command takes no options or arguments, unless a different
441 pd or patchdir is specified. It simply traverses the vpatch directories
442 contained vpatches and returns any leaf vpatches found in the topological
443 pd or patchdir is specified. It simply traverses the vpatches in the
444 vpatch directory and returns any leaf vpatches found in the topological
445 order.
446
447 Examples:
(313 . 7)(342 . 7)
449
450 [ f | flow ]:
451
452 The f or flow command prints a topoligical flow of vpatches based on
453 The f or flow command prints a topological flow of vpatches based on
454 precedence. By default will look for the 'patches' directory in the present
455 working directory of V and print the flow to stdout.
456
(353 . 12)(382 . 12)
458 (<press_dir> <head>)
459
460 The p or press command is available to apply vpatches up through <head> in
461 topological order (see flow command) to an output directory <press_dir>.
462 There are two required arguments; an output directory for applied patches
463 <press_dir> and a vpatch <head> as the tip of the tree to press up through.
464 By default, no output is shown; however if the user supplies `v' or
465 `verbose' directly after the p or press command then the output from the
466 patching applcation process will be directed to stdout.
467 topological order (see press-path command) to an output directory
468 <press_dir>. There are two required arguments; an output directory for
469 applied patches <press_dir> and a vpatch <head> as the tip of the tree to
470 press up through. By default, no output is shown; however if the user
471 supplies `v' or `verbose' directly after the p or press command then the
472 output from the patching application process will be directed to stdout.
473
474 Example:
475 ./v.pl p press_output genesis.vpatch
(382 . 12)(411 . 28)
477 patching file bitcoin/src/init.cpp
478 ...
479
480
481 *** SEE ALSO 'press-path' ***
482
483 [ pp | press-path ]:
484
485 Arguments:
486 (<head>)
487
488 The pp or press-path command is available to allow the user to view (via
489 stdout) the actual path to be pressed, given a <head> found in the flow.
490
491 It is encouraged that a V user run this command before pressing to a given
492 <head>. From release 99993 forward, the flow is no longer used to calculate
493 the press path from a given <head>. Instead, with a given <head>, recurse
494 all of the <head>'s antecedents and press those only.
495
496 [ ss | sync-seals ]:
497
498 Arguments:
499 (<mirror_url> <sdir>)
500
501 The ss or sync-seals command is avilable to allow the user to sync seal to
502 The ss or sync-seals command is available to allow the user to sync seal to
503 an alternative directory. Two arguments are required; the <mirror_url>
504 from which to sync and the alternative or existing seals directory <sdir>.
505
(400 . 7)(445 . 7)
507 Arguments:
508 (<mirror_url> <pdir> <vpatches>... )
509
510 The sv or sync-vpatches command is availabe to allow the user to sync one or
511 The sv or sync-vpatches command is available to allow the user to sync one or
512 more individual vpatches to a alternative output directory. Three arguments
513 are required; the <mirror_url> from which to sync, the alternative or
514 existing directory <pdir> and one or more <vpatches>.
(419 . 7)(464 . 7)
516 Arguments:
517 (<mirror_url> <pdir>)
518
519 The sa or sync-all-vpatches command is avilable to allow the user to sync
520 The sa or sync-all-vpatches command is available to allow the user to sync
521 all vpatches from a given mirror to an alternative output directory. Two
522 arguments are required; the <mirror_url> from which to sync and the
523 alternative or existing patches directory <pdir>.
(492 . 7)(537 . 7)
525 Arguments:
526 (<sha512_hash>)
527
528 The o or origin command is avaliable to allow the user to pass a sha512
529 The o or origin command is available to allow the user to pass a sha512
530 hash and view where the given hash originated in the source tree.
531
532 [ g | graph ]:
(500 . 7)(545 . 7)
534 Arguments & Options:
535 (<output_dotfile> [<output_svg_html_file>])
536
537 The g or graph command is available to produce a topoligical flow graph in
538 The g or graph command is available to produce a topological flow graph in
539 SVG format. The command has a required argument, the <output_dotfile>.
540 The output Dot language file can be used to generate the SVG HTML output
541 file with the `dot` binary. To produce the output Dot language file, the
(510 . 7)(555 . 7)
543 should be available for V to invoke and generate the SVG HTML output for
544 the user automatically. If it is not possible for the user to install
545 'graphviz' on the local environment for whatever reason, the Dot language
546 output file can be copied to a seperate environment where 'graphviz' can be
547 output file can be copied to a separate environment where 'graphviz' can be
548 installed. A command like this is used to generate the SVG HTML output
549 with the `dot` binary: `dot -Tsvg v-graph.dot > v-graph.html`.
550
(530 . 7)(575 . 7)
552 The v or version command simply prints the current version of V to stdout.
553 This command takes no options or arguments.
554
555 [ h | ? | help ]:
556 [ h | help ]:
557
558 The h or ? or help command will print a longer, more verbose help message
559 The h or help command will print a longer, more verbose help message
560 to stdout. This command takes no options or arguments.