[ANN] license_finder 2.0 release candidate ready for testing

20 views
Skip to first unread message

Jacob Maine

unread,
Jan 23, 2015, 7:31:58 PM1/23/15
to license...@googlegroups.com
The first release candidate for license_finder 2.0.0 (rc2) is available on rubygems: https://rubygems.org/gems/license_finder/versions/2.0.0.rc2.  Please install and provide feedback. Read on for release notes and important upgrade instructions.

FEATURES
  • `license_finder` stores every decision made about a project's dependencies, even if a decision was later reverted.  These decisions are kept in an append-only YAML file which can be considered an audit log.
  • Stores timestamps and other optional transactional metadata (who, why) about every kind of decision.
  • When needed, applies those decisions to the list of packages currently reported by the package managers.
  • Removed dependencies on sqlite and sequel.
  • The CLI never writes HTML or CSV reports to the file system, only to STDOUT. So, users have more choice over which reports to generate, when to generate them, and where to put them. See `license_finder report`.  If you would like to update reports automatically (e.g., in a rake task or git hook) see this gist.
  • The configuration YAML file is no longer required, though it can still be useful.  Most of its functionality has been moved into the decisions infrastructure, and the remaining bits can be passed as arguments to the CLI.  Most users will not need these arguments.  If the file is present, the CLI arguments can be omitted.  The CLI no longer updates this file.  Also see this proposal to merge the decisions file with the config file.
BUGFIXES
  • `license_finder` does not write anything to the file system, Issues #94, #114, #117
UPGRADE

To upgrade from `license_finder` version 1.2 to 2.0, see license_finder_upgrade.

To upgrade from a version lower than 1.2, first upgrade to 1.2, and run `license_finder` at least once.  This will ensure that the `license_finder` database is in a state which `license_finder_upgrade` understands.  Then upgrade to 2.0 with `license_finder_upgrade`.
The README for license_finder_upgrade has important post-upgrade information.  In particular,
  • The config file is no longer required for most projects; license_finder_upgrade will delete it if possible.
  • You should delete dependencies.db
  • You may also want to delete unused dependencies.* reports.
-- Jacob Maine
Reply all
Reply to author
Forward
0 new messages