view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

0.089   2022-10-17  Released-By: PERLANCAR; Urgency: medium

        - [ux] Add -e as alias for --eval (--action eval:E).


0.088   2021-06-27  Released-By: PERLANCAR; Urgency: medium

	- Update prereq (renamed module Tree::{To,To::}TextLines).


0.087   2021-02-19  Released-By: PERLANCAR; Urgency: low

	- No functional changes.

	- [dist] Edit Changes: rename Backward-Compatible property in
	  Release Note to Backward-Incompatible.


0.086   2020-04-29  Released-By: PERLANCAR; Urgency: low

	- Tweak Rinci metadata: replace deprecated
	  x.schema.{,element_}entity with more specific schema.


0.085   2020-04-14  Released-By: PERLANCAR; Urgency: medium

Changes  view on Meta::CPAN

0.083   2019-07-30  Released-By: PERLANCAR; Urgency: low

	- [ux] Simplify CLI scripts by disabling read_config & read_env.


0.082   2019-07-29  Released-By: PERLANCAR; Urgency: medium; Backward-Incompatible: yes

	- [refactor][imcompatible change] Extract common subroutine: foosel(),
	  add --select-action, rename --actions to --node-actions, tweak dump
	  output. Rename package varibles.


0.081   2019-07-27  Released-By: PERLANCAR; Urgency: medium

	- Add action: dump.


0.080   2019-07-26  Released-By: PERLANCAR; Urgency: low

LICENSE  view on Meta::CPAN

changed that file, and provided that you do at least ONE of the following:

  a) place your modifications in the Public Domain or otherwise make them
     Freely Available, such as by posting said modifications to Usenet or an
     equivalent medium, or placing the modifications on a major archive site
     such as ftp.uu.net, or by allowing the Copyright Holder to include your
     modifications in the Standard Version of the Package.

  b) use the modified Package only within your corporation or organization.

  c) rename any non-standard executables so the names do not conflict with
     standard executables, which must also be provided, and provide a separate
     manual page for each non-standard executable that clearly documents how it
     differs from the Standard Version.

  d) make other distribution arrangements with the Copyright Holder.

4. You may distribute the programs of this Package in object code or executable
form, provided that you do at least ONE of the following:

  a) distribute a Standard Version of the executables and library files,