--- - branch: MAIN date: Sun Nov 23 14:18:03 UTC 2014 files: - new: '1.11' old: '1.10' path: pkgsrc/databases/p5-App-Sqitch/Makefile pathrev: pkgsrc/databases/p5-App-Sqitch/Makefile@1.11 type: modified - new: '1.7' old: '1.6' path: pkgsrc/databases/p5-App-Sqitch/distinfo pathrev: pkgsrc/databases/p5-App-Sqitch/distinfo@1.7 type: modified id: 20141123T141803Z.80a6cc129dbd6c225588dffa87a9da8392449db2 log: "Update to 0.997. From the changelog:\n\n[New Features]\n- Added support for new target properties. In addition to the existing\n `uri`, `client`, and `registry` properties, targets may also configure\n these properties via the new `--set` option to and `set-*` actions on\n the `target` command:\n * `top_dir`\n * `plan_file`\n * `extension`\n * `deploy_dir`\n * `revert_dir`\n * `verify_dir`\n- Added support for new engine configuration variables. In addition to\n the existing `target`, `client`, and `registry` variables, engine\n configuration may also include these variables:\n * `top_dir`\n * `plan_file`\n * `extension`\n * `deploy_dir`\n * `revert_dir`\n * `verify_dir`\n- Rationalized the hierarchical configuration of deployment targets. The\n properties of any given target will now be determined by examining\n values in the following order:\n * Command-line options\n * Target configuration\n * Engine configuration\n * Core configuration\n \ * Reasonable engine-specific defaults\n- Added the `engine` command to simplify engine configuration. This\n complements the newly-improved `target` command. Run `sqitch engine\n update-config` to update deprecated engine configurations and start\n using it.\n- Added the sqitch-configuration guide to provide an overview of core,\n engine, and target configuration. Includes some use-case examples and\n best suggested practices.\n[Improvements]\n- Simplified the output of `sqitch help`, and added the more important\n options to it.\n- Added the `--guide` option to `sqitch help` to list Sqitch guides.\n- Renamed the `--db-client` option to `--client`. `--db-client` still\n works, but is deprecated.\n- Added the `--registry` core option for parity with `--client`,\n `--top-dir`, `--plan-file`, and the rest of the hierarchical\n configuration properties.\n- Updated the `init` documentation to better cover all the options\n processed.\n- Incremented the version plan file format version to v1.0.0. No changes;\n it has been stable for at least a year, so it's time.\n[Bug Fixes]\n- At runtime, the Vertica engine now properly requires DBD::ODBC\n instead of DBD::Pg.\n- The Vertica engine now supports Vertica 6, as documented.\n- Fixed a warning from Type::Utils, thanks to a report from GÃ\x83©raud\n CONTINSOUZAS.\n- The `status` command once again notices if the specified database is\n uninitialized and says as much, rather than dying with an SQL error.\n- The `--etc-path` option works again.\n[Deprecations]\n- Deprecated `core.$engine` configuration in favor of `engine.$engine`. A\n warning will be emitted if Sqitch sees the former. Run `sqitch engine\n update-config` to update your configurations. Existing `core.$engine`\n configurations will be left in place for compatibility with older\n versions of Sqitch, but the `sqitch engine` command will not modify\n them, so they can get out-of-sync. Run `sqitch config --remove-section\n core.$engine` to remove them.\n- Formally deprecated the database connection options in favor of target\n URIs. If any of these options is used, a warning will be issued. They\n will be dropped in v1.0:\n * `--db-host`\n \ * `--db-port`\n * `--db-username`\n * `--db-password`\n * `--db-name`\n- Formally deprecated the database connection configuration variables in\n favor of target URIs. If any of these variables is used, a warning will\n be issued. Run `sqitch engine update-config` to update your\n configurations. Existing `core.$engine` configurations will be left in\n place for compatibility with older versions of Sqitch, but the `sqitch\n engine` command will not modify them, so they can get out-of-sync. Run\n `sqitch config --remove-section core.$engine` to remove them. Sqitch\n will cease to support them in v1.0:\n * `core.$engine.host`\n \ * `core.$engine.port`\n * `core.$engine.username`\n * `core.$engine.password`\n \ * `core.$engine.db_name`\n- Deprecated the `--registry` and `--client` options of the `target`\n command. All target properties should now be set via the new `--set`\n option, such as `--set registry=reg`.\n- Formally deprecated the following options of the `add` command. They\n have been replaced with the `--with`, `--without`, and `--use` options\n since v0.991. Their use will emit a warning, and they will be removed\n in v1.0:\n * `--deploy-template`\n * `--revert-template`\n * `--verify-template`\n * `--deploy`\n * `--no-deploy`\n * `--revert`\n * `--no-revert`\n \ * `--verify`\n * `--no-verify`\n- Dropped support for the long-deprecated (and likely never used outside\n ancient tests long deleted) engine configuration variables\n `core.sqlite.sqitch_db` and `core.pg.sqitch_schema`. Both have been\n \ replaced with `engine.$engine.registry`, which applies to all engines.\n- Formally deprecated the `@FIRST` and `@LAST` symbolic tags. Their use\n will trigger a warning to use `@ROOT` and `@HEAD`, instead. They will\n be removed in v1.0.\n[Internals]\n- Moved target and engine configuration from App::Sqitch and\n App::Sqitch::Engine to a new class, App::Sqitch::Target. This class is\n solely responsible for finding the appropriate values for attributes on\n every run. The target knows what plan and engine to use, based on those\n properties. App::Sqitch is now responsible solely for encapsulating\n command-line options, configuration, and utilities. Classes are now\n responsible for instantiating both an App::Sqitch and\n App::Sqitch::Target options as appropriate.\n- Updated all classes to create both Sqitch and Target objects as\n appropriate. This change touched almost every class.\n- Replaced attributes in App::Sqitch that were previously set from\n command-line options or configuration with a single attribute,\n `options`, which is a hash only of the command-line options. Classes\n are now responsible for finding the proper values in config or options.\n Mostly this requirement is encapsulated by the new App::Sqitch::Target\n class.\n- Updated the command classes to use either a \"default target\" derived\n from command-line options, engine configuration, and core\n configuration, or a target looked up by name in the configuration\n \ maintained by the `target` command.\n- Fixed one more test failure due to the introduction of \"Negative repeat\n count does nothing\" warning in Perl 5.21.1.\n- Fixed \"Redundant argument in printf\" warning on Perl 5.21.2.\n- Switched from Digest::SHA1, which is deprecated, to Digest::SHA for\n generating SHA-1 IDs.\n- Switched from Mouse and Moose to Moo. Sqitch no longer depends on any\n modules that use Moose, either. This results in an approximately 40%\n startup time speedup.\n- Loading of App::Sqitch::DateTime is now deferred until it's needed.\n This is because DateTime is rather expensive to load. Since a number of\n commands don't need it, it seems silly to load it in those cases.\n- Now recommend Type::Tiny::XS and Class::XSAccessor for improved\n performance.\n- The `check` command now properly fails on a plan parse error, instead\n of blindly continuing on.\n- Fixed a failing test on PosrgreSQL due to localization issues. Thanks\n to Sven Schoberf for the report (Issue #171).\n- Added the `revert.prompt_accept`, `rebase.prompt_accept`, and\n `checkout.prompt_accept` boolean configuration variables. Set these\n variables to false to change the default answer to the revert prompt to\n \"No\". When rebasing or checking out, if the variables specific to those\n commands are not set, Sqitch will fall back on the value of\n `revert.prompt_accept`. Suggested by Graeme Lawton (Issue #164).\n- The MySQL engine now sets the `$MYSQL_PWD` environment variable if a\n password is provided in a target. This should simplify authtentication\n \ when running MySQL change scripts through the `mysql` client client\n (Issue #150).\n- The MySQL engine now reads `client` and `mysql` groups in the MySQL\n \ configuration files for a password when connecting to the registry\n database, and when the target URI includes no password. The MySQL\n client already read those files, of course, but now the internal\n database connection does as well (Issue #150).\n- The Firebird engine now sets the `$ISC_PASSWORD` environment variable\n if a password is provided in a target. This should simplify\n authtentication when running Firebird change scripts through the `isql`\n client client. Patch from È\x98tefan Suciu.\n- No longer passing URI query params as DBI params, because they are\n already included in the DSN provided by URI::db.\n- Added the Vertica engine.\n" module: pkgsrc subject: 'CVS commit: pkgsrc/databases/p5-App-Sqitch' unixtime: '1416752283' user: schmonz