-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I'm happy to announce a new version of V: version 99993 K Changes included with V version 99993 K: 0x00]: Updated the date of TMSR copyright. 0x01]: Updated the version number of the vtron to 99993 K. 0x02]: Grammatical/Spelling errors fixed. Thanks to hanbot for finding these. 0x03]: There is a significant change to the manner in which we handle the creation of temp directory for holding the temporary life (during the execution of V, and no longer) of the gpg keyring. This entails removing the code that looks up the users home directory and creation of a directory called '~/.gnupgtmp'. Instead, we are now making use of the UNIX `mktemp` utility. We now attempt to use `mktemp` to create a temporary directory in the /tmp filesystem if it exists. If it does not exist, for whatever reason, it will attempt to create the temporary directory in the same place where V is executed from, '.'. 0x04]: As it turns out, modern ``unix'' environments ship completely useless without any sensible utilities at all. Various unfortunate persons have found this out the hard way. My vtron uses various shell-outs to execute tasks, so a 'check_required_bins' subroutine has been added to execute first to ensure that all the necessary binaries are available on the users local system. If a dependent program is not found, an error message will be printed letting the user know which is missing. 0x05]: A defect has been found [R.01], and reported [R.02] in all previous versions of my vtron. The defect, in a nutshell, is that if you have more than one leaf in your vpatch flow, and you select to press all of the way through the flow, you could end up pressing leafs that you didn't intend to press. To shed a bit more light on this, now when a user goes to press, the flow will not be used to calculate the press-path. Instead, with a given HEAD from the user, my vtron will now recurse the vtree finding all it's antecedents and press those only. To aid the user, for the time being, I have added a subroutine to the system called 'press-path' or 'pp'. If the user wants to see ~EXACTLY~ what will be pressed, in what exact order, the user can use 'press-path' or 'pp' with a given HEAD, and the vpatches will be printed to standard out. 0x06]: Results From Testing The changes have been tested in a combintion of manual and automated test suite. The automated test suite is available upon request. I would like to thank: shinohai, diana_coman, hanbot, and asciilifeform for their efforts in testing and review of the changes. If you have questions or comments please ask mod6 in #trilema, or via email. 0x07]: Attached to this email The following are attached to this email with their PGP signatures: v.pl v.pl.mod6.sig v_quick_start.txt v_quick_start.txt.mod6.sig v_users_manual.txt v_users_manual.txt.mod6.sig V-20180222.tar.gz V-20180222.tar.gz.mod6.sig Enjoy! 0x08]: References [R.01]: http://btcbase.org/log/2017-12-22#1756251 [R.02]: http://thebitcoin.foundation/ml/btc-dev/2018-January/000285.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iQIcBAEBCgAGBQJaj0NyAAoJEHIXBai3Hq2v2zgP/0d6wUzOocFN0/QVZRsS78xz m1o22T+Vb3sAOvHTx/3RK//wRK0332eqQV2ceEc7FTVl8U5Nk0MBzF9UISvTvgW+ tMMYLFvaEGF+/ie6ASWmUMylGLM6/N80qHVvodDEBPylObtcpknrK9twQemy2x5n Xpdvr4QoO2F+l4Ak1tGpSSAMkW6iKI5xPx01dmsAY1ARpj8WKXw4nduSL9d6L8qf 4inGCGaW5jW7IcyyYmfnXroVQMQA+nLmK5Annr9RLJh4YWSnWop4eyxSizQbDVzK JIQHrOU5F66UMTw+yOpHyyIzbRj08WvXPLiSSCP0tgp2oxsmJzJQ8Nw0a/2OTkrH MNjBWvWHteARPOpW5bbbTVt8d4HBAzIx3wGbMY1GnANHG8z2CWlCvcxWsgu9vhBL wNLfmo/84Yj+BdeTfzNPyLvr6FrGmhI0KtmHOpW9YWf+Z0OWyxkkV1kKA/xrFmam ko5Z2GgvrvPmdj9K48e9CVx1gs/bIg4ahRcTQ77NKiDGa+NxPL9zVLkF3KCqtUhG BQDhFM5rQKz7ncHUKkfDc5WUq9jel7py2ksA/XHqVGixNLPacnEiaiJGKcot9zaS +Wsz9BrYH4cO6prenUxJBj2Tcx2t7jibZL0wMIdX3DQ4MO4CMnd0UL7rhTtjb2hb s/JQEun93sb25Al+0kaZ =uUeQ -----END PGP SIGNATURE-----