Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
Changes from previous:
----------------------
0.91: 17 May 2011
- Support calling commands noninteractively (patch by Christian Kuelker)
- Support calling $term->run() multiple times (patch by Ryan Gies)
- Now clients can call process_a_cmd manually (patch by Martin Kluge)
- Undeprecate Term::ReadLine::Perl since it works on Windows.
0.9: 20 Mar 2011
- Relicensed from the somewhat ambiguous Perl license to the MIT license.
- Add eof_exit_hooks, patch by Lester Hightower
- Remove complete_history callback. It was an odd, ShellUI-specific feature.
- Remove history expansion (!!, !$, ^o^n). That implementation was too buggy.
- Fix bug: completion suggestion wasn't printed with Term::ReadLine::Gnu.
- Deprecate Term::ReadLine::Perl. Use Term::ReadLine::Gnu.
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
Packaged by Edgar Fuss and provided by PR 39827.
Term::ShellUI uses the history and autocompletion features of Term::ReadLine to
present a sophisticated command-line interface to the user. It tries to make
every feature that one would expect to see in a fully interactive shell trivial
$to implement. You simply declare your command set and let ShellUI take care
of the heavy lifting.
This module was previously called Term::GDBUI.
