--- - branch: MAIN date: Tue Jul 11 10:18:38 UTC 2017 files: - new: '1.12' old: '1.11' path: pkgsrc/devel/ocaml-cmdliner/Makefile pathrev: pkgsrc/devel/ocaml-cmdliner/Makefile@1.12 type: modified - new: '1.3' old: '1.2' path: pkgsrc/devel/ocaml-cmdliner/PLIST pathrev: pkgsrc/devel/ocaml-cmdliner/PLIST@1.3 type: modified - new: '1.8' old: '1.7' path: pkgsrc/devel/ocaml-cmdliner/buildlink3.mk pathrev: pkgsrc/devel/ocaml-cmdliner/buildlink3.mk@1.8 type: modified - new: '1.4' old: '1.3' path: pkgsrc/devel/ocaml-cmdliner/distinfo pathrev: pkgsrc/devel/ocaml-cmdliner/distinfo@1.4 type: modified id: 20170711T101838Z.c2f8f9169d7a8f0aabedb554d585bb8ec22204c1 log: "Updated package to latest version, 1.0.0. Changes include:\n\nv1.0.0 2017-03-02 La Forclaz (VS)\n---------------------------------\n\n**IMPORTANT** The `Arg.converter` type is deprecated in favor of the\n`Arg.conv` type. For this release both types are equal but the next\nmajor release will drop the former and make the latter abstract. All\nusers are kindly requested to migrate to use the new type and **only**\nvia the new `Arg.[p]conv` and `Arg.conv_{parser,printer}` functions.\n\n- Allow terms to be used more than once in terms without tripping out\n documentation generation (#77). Thanks to Franå·½ois Bobot and Gabriel\n Radanne.\n- Disallow defining the same option (resp. command) name twice via two\n different arguments (resp. terms). Raises Invalid_argument, used\n to be undefined behaviour (in practice, an arbitrary one would be\n ignored).\n- Improve converter API (see important message above).\n- Add `Term.exit[_status]` and `Term.exit_status_of[_status]_result`.\n \ improves composition with `Pervasives.exit`.\n- Add `Term.term_result` and `Term.cli_parse_result` improves composition\n with terms evaluating to `result` types.\n- Add `Arg.parser_of_kind_of_string`.\n- Change semantics of `Arg.pos_left` (see #76 for details).\n- Deprecate `Term.man_format` in favor of `Arg.man_format`.\n- Reserve the `--cmdliner` option for library use. This is unused for now\n but will be in the future.\n- Relicense from BSD3 to ISC.\n- Safe-string support.\n- Build depend on topkg.\n\n### End-user visible changes\n\nThe following changes affect the end-user behaviour of all binaries using\ncmdliner.\n\n- Required positional arguments. All missing required position\n \ arguments are now reported to the end-user, in the correct\n order (#39). Thanks to Dmitrii Kashin for the report.\n- Optional arguments. All unknown and ambiguous optional argument\n arguments are now reported to the end-user (instead of only\n \ the first one).\n- Change default behaviour of `--help[=FMT]` option. `FMT` no longer\n defaults to `pager` if unspecified. It defaults to the new value\n \ `auto` which prints the help as `pager` or `plain` whenever the\n `TERM` environment variable is `dumb` or undefined (#43). At the API\n level this changes the signature of the type `Term.ret` and values\n `Term.ret`, `Term.man_format` (deprecated) and `Manpage.print` to add the\n new `` `Auto`` case to manual formats. These are now represented by the\n `Manpage.format` type rather than inlined polyvars.\n\n### Doc specification improvements and fixes\n\n- Add `?envs` optional argument to `Term.info`. Documents environment\n variables that influence a term's evaluation and automatically\n integrate them in the manual.\n- Add `?exits` optional argument to `Term.info`. Documents exit statuses of\n the program. Use `Term.default_exits` if you are using the new `Term.exit`\n functions.\n- Add `?man_xrefs` optional argument to `Term.info`. Documents\n references to other manpages. Automatically formats a `SEE ALSO` section\n in the manual.\n- Add `Manpage.escape` to escape a string from the documentation markup\n language.\n- Add `Manpage.s_*` constants for standard man page section names.\n- Add a `` `Blocks`` case to `Manpage.blocks` to allow block splicing\n (#69). This avoids having to concatenate block lists at the\n toplevel of your program.\n- `Arg.env_var`, change default environment variable section to the\n standard `ENVIRONMENT` manual section rather than `ENVIRONMENT\n VARIABLES`. If you previously manually positioned that section in\n your man page you will have to change the name. See also next point.\n- Fix automatic placement of default environment variable section (#44)\n whenever unspecified in the man page.\n- Better automatic insertions of man page sections (#73). See the API\n docs about manual specification. As a side effect the `NAME` section\n can now also be overriden manually.\n- Fix repeated environment variable printing for flags (#64). Thanks to\n Thomas Gazagnaire for the report.\n- Fix rendering of env vars in man pages, bold is standard (#71).\n- Fix plain help formatting for commands with empty\n description. Thanks to Maciek Starzyk for the patch.\n- Fix (implement really) groff man page escaping (#48).\n- Request `an` macros directly in the man page via `.mso` this\n makes man pages self-describing and avoids having to call `groff` with\n the `-man` option.\n- Document required optional arguments as such (#82). Thanks to Isaac Hodes\n for the report.\n\n### Doc language sanitization\n\nThis release tries to bring sanity to the doc language. This may break\nthe rendering of some of your man pages. Thanks to Gabriel Scherer,\nIvan Gotovchits and Nicolå\x8F©s Ojeda Bè¾°r for the feedback.\n\n- It is only allowed to use the variables `$(var)` that are mentioned in\n the docs (`$(docv)`, `$(opt)`, etc.) and the markup directives\n `$({i,b},text)`. Any other unknown `$(var)` will generate errors\n on standard error during documentation generation.\n- Markup directives `$({i,b},text)` treat `text` as is, modulo escapes;\n see next point.\n- Characters `$`, `(`, `)` and `\\` can respectively be escaped by `\\$`,\n \ `\\(`, `\\)` and `\\\\`. Escaping `$` and `\\` is mandatory everywhere.\n Escaping `)` is mandatory only in markup directives. Escaping `(`\n is only here for your symmetric pleasure. Any other sequence of\n character starting with a `\\` is an illegal sequence.\n- Variables `$(mname)` and `$(tname)` are now marked up with bold when\n substituted. If you used to write `$(b,$(tname))` this will generate\n an error on standard output, since `$` is not escaped in the markup\n \ directive. Simply replace these by `$(tname)`.\n" module: pkgsrc subject: 'CVS commit: pkgsrc/devel/ocaml-cmdliner' unixtime: '1499768318' user: jaapb