2014-03-13 12:08:49 +01:00
|
|
|
# $NetBSD: Makefile,v 1.31 2014/03/13 11:08:51 jperkin Exp $
|
Initial import of tcl-expect-5.32.1, the tcl half of the new expect packages.
Changes to the expect package since expect-5.25:
* This package is now split into two packages, tcl-expect, and
tk-expect. tcl-expect can be installed on systems without
X11 (and by extension, without tk).
* the copious expect examples and their man pages are now installed
into ${PREFIX}/share/examples/tcl/expect instead of into
${PREFIX}/bin and ${PREFIX}/man. If any of them are determined
to be worth separate use, they should be split out into a
separate package.
Changes to expect itself since expect-5.25:
** SUMMARY
Expect 5.31 now works with Tcl 8.2. Expect 5.31 does NOT work with
prior releases of Tcl. Thanks to an incredible amount of work by
Scott Stanton, Henry Spencer, Melissa Hirschl, and funding from
Scriptics for making this possible.
** NEW FEATURES
What? You mean that working with Tcl 8.2 isn't enough?????
Expect supports Tcl's new regexp engine.
Expect supports null bytes in strings directly. (You no longer have
to use the "null" keyword to send or match nulls. Of course, the
"null" keyword will continue to be supported.) Null removal (on
input) is still enabled by default since nulls are almost never
intended for end-user consumption in interactive dialogues.
** CHANGES IN BEHAVIOR (POTENTIAL INCOMPATIBILITIES)
The interpreter command used to exit upon eof. Now it uses "-eof
script" to control this behavior. The default behavior is to return.
(This change was required because Expect now gives control to Tcl upon
exit and Tcl waits (potentially forever) for all processes to die on
exit.) Explicit calls to interpreter are almost non-existent.
However, you should look for *implicit* calls via interact commands
with a pattern but no action. This required changes in the examples:
dislocate, dvorak, kibitz, and xkibitz.
Indirect variables can no longer start with "exp". Such variables
will be interpreted as channel names.
Old-style regexps may need conversion. If you have been protecting
regexps containing backslashes with {}, then you need to examine all
your backslashes since the new regexp engine interprets backslash
sequences (such as \n) itself. For example:
expect "\n" (works the same in Tcl 8.0 and 8.1)
expect {\n} (works differently in Tcl 8.0 and 8.1)
Scriptics has also created a new-regexp-features page which you should
read: http://www.scriptics.com/support/howto/regexp81.html. Some of
the new features allow much more efficient regexps than before. For
example, non-greedy quantifiers can replace [split] looping
constructions with a single regexp, enabling Tcl to parse very
efficiently. For the whole story, read the re_syntax man page.
The interact command's regexp matching no longer skips nulls. (I'd be
surprised if anyone misses this. At least I hope ....)
Expect's C library now reports failures in spawn's underlying exec
directly (by returning -1) rather than the way it used to (as data in
the pty). This makes user code more robust. However, it requires you
to simplify your code, alas. See the chesslib.c example.
Linking with Expect's C library no longer requires the Tcl library
(unless, of course, you make Tcl calls yourself). Tcl is still
required to build the library in the first place, however.
** CHANGES IN BEHAVIOR (SHOULD NOT CAUSE INCOMPATIBILITIES)
The match_max command now controls by bytes, not chars. This won't
cause problems unless your existing scripts are interacting using
sizeable chunks of multibyte characters. (If you don't know what I'm
talking about, ignore this.)
The Make/configure suite now corresponds to the TEA conventions (at
least in theory; the conventions are changing regularly so it's hard
to be less vague on this point). Significantly, this means that you
should be able to use the same configure flags as when compiling Tcl
or any other TEA-compatible extension. (See the INSTALL file.)
The values of special variables such as exp_spawn_id_any have changed.
(The values were never documented so you shouldn't have been using
them anyway.)
Spawn ids now appear as "exp...". (They used to be small integers.)
Do not assume that spawn ids will continue to be represented in any
particular way (other than unique strings).
** OTHER NOTES
Expect uses channels. There is an Expect channel type. It is
possible to use Tcl's channel commands, such as fconfigure, to change
the encoding. However, Expect layers its own buffering system on top
of Tcl's channel handler so don't expect intuitive behavior when using
commands such as gets and puts. Unless you know what you're doing, I
recommend manipulating the Expect channels only with the expect
commands.
Some effort was made to make Expect support threads, however it is not
complete. You can compile Expect with threads enabled but don't run
Expect in multiple threads just yet.
So much code has changed, there are bound to be bugs in dark corners.
Please let me know of such cases. The best response will come by
supplying a simple test case that can be added to Expect's test suite.
In places where the behavior of Expect was not precisely documented,
full advantage was taken to do something different :-)
Several esoteric bugs were fixed.
Although Expect itself uses Henry Spencer's new regexp engine,
Expect's C library still uses his original regexp engine.
No testing has been done of the poll and non-event subsystems. (These
are used on systems which don't support select on ptys or ttys. Some
minor work needs to be done on them (because the event subsystem was
rewritten) which I'll probably do only if anyone requests it.
Many deprecated features (deprecated for many years!) have been
removed. All such features were deprecated prior to Exploring Expect
so if that's how you learned Expect, you have nothing to worry about.
For example, Expect's getpid command predates Tcl's pid command and
it's been deprecated for, oh.... 6 years - wow! Other deprecated features
include:
expect -timestamp (flag only; behavior itself was removed years ago)
expect -iwrite (flag only; behavior occurs all the time)
expect_version (use "exp_version" command)
expect_library (use "exp_library" global variable)
interact -eof (use "eof" keyword)
interact -timeout (use "timeout" keyword)
interact -timestamp (use "clock" command)
getpid (use "pid" command)
system stty (use "stty" command)
With this release, the following are deprecated:
timestamp (use "clock" command)
debugger (use a different one; there are very nice replacements
around. Fortunately the Expect debugger is not something anyone
is wiring into their scripts, so for now, consider it on the
endangered species list. Anyone still want this debugger?)
From now on, the most current snapshots of Expect will be found in the
Scriptics CVS repository. Not all snapshots are official releases.
For more, see the ChangeLog file in the expect distribution.
2000-09-05 18:20:29 +02:00
|
|
|
|
2003-01-28 04:41:02 +01:00
|
|
|
.include "Makefile.common"
|
|
|
|
|
|
|
|
|
|
PKGNAME= tcl-expect-${EXPECT_VERSION}
|
2014-01-11 15:42:00 +01:00
|
|
|
PKGREVISION= 3
|
Initial import of tcl-expect-5.32.1, the tcl half of the new expect packages.
Changes to the expect package since expect-5.25:
* This package is now split into two packages, tcl-expect, and
tk-expect. tcl-expect can be installed on systems without
X11 (and by extension, without tk).
* the copious expect examples and their man pages are now installed
into ${PREFIX}/share/examples/tcl/expect instead of into
${PREFIX}/bin and ${PREFIX}/man. If any of them are determined
to be worth separate use, they should be split out into a
separate package.
Changes to expect itself since expect-5.25:
** SUMMARY
Expect 5.31 now works with Tcl 8.2. Expect 5.31 does NOT work with
prior releases of Tcl. Thanks to an incredible amount of work by
Scott Stanton, Henry Spencer, Melissa Hirschl, and funding from
Scriptics for making this possible.
** NEW FEATURES
What? You mean that working with Tcl 8.2 isn't enough?????
Expect supports Tcl's new regexp engine.
Expect supports null bytes in strings directly. (You no longer have
to use the "null" keyword to send or match nulls. Of course, the
"null" keyword will continue to be supported.) Null removal (on
input) is still enabled by default since nulls are almost never
intended for end-user consumption in interactive dialogues.
** CHANGES IN BEHAVIOR (POTENTIAL INCOMPATIBILITIES)
The interpreter command used to exit upon eof. Now it uses "-eof
script" to control this behavior. The default behavior is to return.
(This change was required because Expect now gives control to Tcl upon
exit and Tcl waits (potentially forever) for all processes to die on
exit.) Explicit calls to interpreter are almost non-existent.
However, you should look for *implicit* calls via interact commands
with a pattern but no action. This required changes in the examples:
dislocate, dvorak, kibitz, and xkibitz.
Indirect variables can no longer start with "exp". Such variables
will be interpreted as channel names.
Old-style regexps may need conversion. If you have been protecting
regexps containing backslashes with {}, then you need to examine all
your backslashes since the new regexp engine interprets backslash
sequences (such as \n) itself. For example:
expect "\n" (works the same in Tcl 8.0 and 8.1)
expect {\n} (works differently in Tcl 8.0 and 8.1)
Scriptics has also created a new-regexp-features page which you should
read: http://www.scriptics.com/support/howto/regexp81.html. Some of
the new features allow much more efficient regexps than before. For
example, non-greedy quantifiers can replace [split] looping
constructions with a single regexp, enabling Tcl to parse very
efficiently. For the whole story, read the re_syntax man page.
The interact command's regexp matching no longer skips nulls. (I'd be
surprised if anyone misses this. At least I hope ....)
Expect's C library now reports failures in spawn's underlying exec
directly (by returning -1) rather than the way it used to (as data in
the pty). This makes user code more robust. However, it requires you
to simplify your code, alas. See the chesslib.c example.
Linking with Expect's C library no longer requires the Tcl library
(unless, of course, you make Tcl calls yourself). Tcl is still
required to build the library in the first place, however.
** CHANGES IN BEHAVIOR (SHOULD NOT CAUSE INCOMPATIBILITIES)
The match_max command now controls by bytes, not chars. This won't
cause problems unless your existing scripts are interacting using
sizeable chunks of multibyte characters. (If you don't know what I'm
talking about, ignore this.)
The Make/configure suite now corresponds to the TEA conventions (at
least in theory; the conventions are changing regularly so it's hard
to be less vague on this point). Significantly, this means that you
should be able to use the same configure flags as when compiling Tcl
or any other TEA-compatible extension. (See the INSTALL file.)
The values of special variables such as exp_spawn_id_any have changed.
(The values were never documented so you shouldn't have been using
them anyway.)
Spawn ids now appear as "exp...". (They used to be small integers.)
Do not assume that spawn ids will continue to be represented in any
particular way (other than unique strings).
** OTHER NOTES
Expect uses channels. There is an Expect channel type. It is
possible to use Tcl's channel commands, such as fconfigure, to change
the encoding. However, Expect layers its own buffering system on top
of Tcl's channel handler so don't expect intuitive behavior when using
commands such as gets and puts. Unless you know what you're doing, I
recommend manipulating the Expect channels only with the expect
commands.
Some effort was made to make Expect support threads, however it is not
complete. You can compile Expect with threads enabled but don't run
Expect in multiple threads just yet.
So much code has changed, there are bound to be bugs in dark corners.
Please let me know of such cases. The best response will come by
supplying a simple test case that can be added to Expect's test suite.
In places where the behavior of Expect was not precisely documented,
full advantage was taken to do something different :-)
Several esoteric bugs were fixed.
Although Expect itself uses Henry Spencer's new regexp engine,
Expect's C library still uses his original regexp engine.
No testing has been done of the poll and non-event subsystems. (These
are used on systems which don't support select on ptys or ttys. Some
minor work needs to be done on them (because the event subsystem was
rewritten) which I'll probably do only if anyone requests it.
Many deprecated features (deprecated for many years!) have been
removed. All such features were deprecated prior to Exploring Expect
so if that's how you learned Expect, you have nothing to worry about.
For example, Expect's getpid command predates Tcl's pid command and
it's been deprecated for, oh.... 6 years - wow! Other deprecated features
include:
expect -timestamp (flag only; behavior itself was removed years ago)
expect -iwrite (flag only; behavior occurs all the time)
expect_version (use "exp_version" command)
expect_library (use "exp_library" global variable)
interact -eof (use "eof" keyword)
interact -timeout (use "timeout" keyword)
interact -timestamp (use "clock" command)
getpid (use "pid" command)
system stty (use "stty" command)
With this release, the following are deprecated:
timestamp (use "clock" command)
debugger (use a different one; there are very nice replacements
around. Fortunately the Expect debugger is not something anyone
is wiring into their scripts, so for now, consider it on the
endangered species list. Anyone still want this debugger?)
From now on, the most current snapshots of Expect will be found in the
Scriptics CVS repository. Not all snapshots are official releases.
For more, see the ChangeLog file in the expect distribution.
2000-09-05 18:20:29 +02:00
|
|
|
CATEGORIES= lang
|
|
|
|
|
|
2009-08-20 17:24:58 +02:00
|
|
|
MAINTAINER= pkgsrc-users@NetBSD.org
|
2003-07-21 18:45:54 +02:00
|
|
|
COMMENT= Extensions to Tcl to support scripting of interactive programs
|
2012-08-21 23:33:58 +02:00
|
|
|
LICENSE= public-domain
|
Initial import of tcl-expect-5.32.1, the tcl half of the new expect packages.
Changes to the expect package since expect-5.25:
* This package is now split into two packages, tcl-expect, and
tk-expect. tcl-expect can be installed on systems without
X11 (and by extension, without tk).
* the copious expect examples and their man pages are now installed
into ${PREFIX}/share/examples/tcl/expect instead of into
${PREFIX}/bin and ${PREFIX}/man. If any of them are determined
to be worth separate use, they should be split out into a
separate package.
Changes to expect itself since expect-5.25:
** SUMMARY
Expect 5.31 now works with Tcl 8.2. Expect 5.31 does NOT work with
prior releases of Tcl. Thanks to an incredible amount of work by
Scott Stanton, Henry Spencer, Melissa Hirschl, and funding from
Scriptics for making this possible.
** NEW FEATURES
What? You mean that working with Tcl 8.2 isn't enough?????
Expect supports Tcl's new regexp engine.
Expect supports null bytes in strings directly. (You no longer have
to use the "null" keyword to send or match nulls. Of course, the
"null" keyword will continue to be supported.) Null removal (on
input) is still enabled by default since nulls are almost never
intended for end-user consumption in interactive dialogues.
** CHANGES IN BEHAVIOR (POTENTIAL INCOMPATIBILITIES)
The interpreter command used to exit upon eof. Now it uses "-eof
script" to control this behavior. The default behavior is to return.
(This change was required because Expect now gives control to Tcl upon
exit and Tcl waits (potentially forever) for all processes to die on
exit.) Explicit calls to interpreter are almost non-existent.
However, you should look for *implicit* calls via interact commands
with a pattern but no action. This required changes in the examples:
dislocate, dvorak, kibitz, and xkibitz.
Indirect variables can no longer start with "exp". Such variables
will be interpreted as channel names.
Old-style regexps may need conversion. If you have been protecting
regexps containing backslashes with {}, then you need to examine all
your backslashes since the new regexp engine interprets backslash
sequences (such as \n) itself. For example:
expect "\n" (works the same in Tcl 8.0 and 8.1)
expect {\n} (works differently in Tcl 8.0 and 8.1)
Scriptics has also created a new-regexp-features page which you should
read: http://www.scriptics.com/support/howto/regexp81.html. Some of
the new features allow much more efficient regexps than before. For
example, non-greedy quantifiers can replace [split] looping
constructions with a single regexp, enabling Tcl to parse very
efficiently. For the whole story, read the re_syntax man page.
The interact command's regexp matching no longer skips nulls. (I'd be
surprised if anyone misses this. At least I hope ....)
Expect's C library now reports failures in spawn's underlying exec
directly (by returning -1) rather than the way it used to (as data in
the pty). This makes user code more robust. However, it requires you
to simplify your code, alas. See the chesslib.c example.
Linking with Expect's C library no longer requires the Tcl library
(unless, of course, you make Tcl calls yourself). Tcl is still
required to build the library in the first place, however.
** CHANGES IN BEHAVIOR (SHOULD NOT CAUSE INCOMPATIBILITIES)
The match_max command now controls by bytes, not chars. This won't
cause problems unless your existing scripts are interacting using
sizeable chunks of multibyte characters. (If you don't know what I'm
talking about, ignore this.)
The Make/configure suite now corresponds to the TEA conventions (at
least in theory; the conventions are changing regularly so it's hard
to be less vague on this point). Significantly, this means that you
should be able to use the same configure flags as when compiling Tcl
or any other TEA-compatible extension. (See the INSTALL file.)
The values of special variables such as exp_spawn_id_any have changed.
(The values were never documented so you shouldn't have been using
them anyway.)
Spawn ids now appear as "exp...". (They used to be small integers.)
Do not assume that spawn ids will continue to be represented in any
particular way (other than unique strings).
** OTHER NOTES
Expect uses channels. There is an Expect channel type. It is
possible to use Tcl's channel commands, such as fconfigure, to change
the encoding. However, Expect layers its own buffering system on top
of Tcl's channel handler so don't expect intuitive behavior when using
commands such as gets and puts. Unless you know what you're doing, I
recommend manipulating the Expect channels only with the expect
commands.
Some effort was made to make Expect support threads, however it is not
complete. You can compile Expect with threads enabled but don't run
Expect in multiple threads just yet.
So much code has changed, there are bound to be bugs in dark corners.
Please let me know of such cases. The best response will come by
supplying a simple test case that can be added to Expect's test suite.
In places where the behavior of Expect was not precisely documented,
full advantage was taken to do something different :-)
Several esoteric bugs were fixed.
Although Expect itself uses Henry Spencer's new regexp engine,
Expect's C library still uses his original regexp engine.
No testing has been done of the poll and non-event subsystems. (These
are used on systems which don't support select on ptys or ttys. Some
minor work needs to be done on them (because the event subsystem was
rewritten) which I'll probably do only if anyone requests it.
Many deprecated features (deprecated for many years!) have been
removed. All such features were deprecated prior to Exploring Expect
so if that's how you learned Expect, you have nothing to worry about.
For example, Expect's getpid command predates Tcl's pid command and
it's been deprecated for, oh.... 6 years - wow! Other deprecated features
include:
expect -timestamp (flag only; behavior itself was removed years ago)
expect -iwrite (flag only; behavior occurs all the time)
expect_version (use "exp_version" command)
expect_library (use "exp_library" global variable)
interact -eof (use "eof" keyword)
interact -timeout (use "timeout" keyword)
interact -timestamp (use "clock" command)
getpid (use "pid" command)
system stty (use "stty" command)
With this release, the following are deprecated:
timestamp (use "clock" command)
debugger (use a different one; there are very nice replacements
around. Fortunately the Expect debugger is not something anyone
is wiring into their scripts, so for now, consider it on the
endangered species list. Anyone still want this debugger?)
From now on, the most current snapshots of Expect will be found in the
Scriptics CVS repository. Not all snapshots are official releases.
For more, see the ChangeLog file in the expect distribution.
2000-09-05 18:20:29 +02:00
|
|
|
|
2014-03-13 12:08:49 +01:00
|
|
|
USE_GCC_RUNTIME= yes
|
|
|
|
|
|
2005-04-08 13:54:04 +02:00
|
|
|
CONFIGURE_ARGS+= --enable-shared
|
2007-02-22 20:26:05 +01:00
|
|
|
CONFIGURE_ARGS+= --without-x
|
Initial import of tcl-expect-5.32.1, the tcl half of the new expect packages.
Changes to the expect package since expect-5.25:
* This package is now split into two packages, tcl-expect, and
tk-expect. tcl-expect can be installed on systems without
X11 (and by extension, without tk).
* the copious expect examples and their man pages are now installed
into ${PREFIX}/share/examples/tcl/expect instead of into
${PREFIX}/bin and ${PREFIX}/man. If any of them are determined
to be worth separate use, they should be split out into a
separate package.
Changes to expect itself since expect-5.25:
** SUMMARY
Expect 5.31 now works with Tcl 8.2. Expect 5.31 does NOT work with
prior releases of Tcl. Thanks to an incredible amount of work by
Scott Stanton, Henry Spencer, Melissa Hirschl, and funding from
Scriptics for making this possible.
** NEW FEATURES
What? You mean that working with Tcl 8.2 isn't enough?????
Expect supports Tcl's new regexp engine.
Expect supports null bytes in strings directly. (You no longer have
to use the "null" keyword to send or match nulls. Of course, the
"null" keyword will continue to be supported.) Null removal (on
input) is still enabled by default since nulls are almost never
intended for end-user consumption in interactive dialogues.
** CHANGES IN BEHAVIOR (POTENTIAL INCOMPATIBILITIES)
The interpreter command used to exit upon eof. Now it uses "-eof
script" to control this behavior. The default behavior is to return.
(This change was required because Expect now gives control to Tcl upon
exit and Tcl waits (potentially forever) for all processes to die on
exit.) Explicit calls to interpreter are almost non-existent.
However, you should look for *implicit* calls via interact commands
with a pattern but no action. This required changes in the examples:
dislocate, dvorak, kibitz, and xkibitz.
Indirect variables can no longer start with "exp". Such variables
will be interpreted as channel names.
Old-style regexps may need conversion. If you have been protecting
regexps containing backslashes with {}, then you need to examine all
your backslashes since the new regexp engine interprets backslash
sequences (such as \n) itself. For example:
expect "\n" (works the same in Tcl 8.0 and 8.1)
expect {\n} (works differently in Tcl 8.0 and 8.1)
Scriptics has also created a new-regexp-features page which you should
read: http://www.scriptics.com/support/howto/regexp81.html. Some of
the new features allow much more efficient regexps than before. For
example, non-greedy quantifiers can replace [split] looping
constructions with a single regexp, enabling Tcl to parse very
efficiently. For the whole story, read the re_syntax man page.
The interact command's regexp matching no longer skips nulls. (I'd be
surprised if anyone misses this. At least I hope ....)
Expect's C library now reports failures in spawn's underlying exec
directly (by returning -1) rather than the way it used to (as data in
the pty). This makes user code more robust. However, it requires you
to simplify your code, alas. See the chesslib.c example.
Linking with Expect's C library no longer requires the Tcl library
(unless, of course, you make Tcl calls yourself). Tcl is still
required to build the library in the first place, however.
** CHANGES IN BEHAVIOR (SHOULD NOT CAUSE INCOMPATIBILITIES)
The match_max command now controls by bytes, not chars. This won't
cause problems unless your existing scripts are interacting using
sizeable chunks of multibyte characters. (If you don't know what I'm
talking about, ignore this.)
The Make/configure suite now corresponds to the TEA conventions (at
least in theory; the conventions are changing regularly so it's hard
to be less vague on this point). Significantly, this means that you
should be able to use the same configure flags as when compiling Tcl
or any other TEA-compatible extension. (See the INSTALL file.)
The values of special variables such as exp_spawn_id_any have changed.
(The values were never documented so you shouldn't have been using
them anyway.)
Spawn ids now appear as "exp...". (They used to be small integers.)
Do not assume that spawn ids will continue to be represented in any
particular way (other than unique strings).
** OTHER NOTES
Expect uses channels. There is an Expect channel type. It is
possible to use Tcl's channel commands, such as fconfigure, to change
the encoding. However, Expect layers its own buffering system on top
of Tcl's channel handler so don't expect intuitive behavior when using
commands such as gets and puts. Unless you know what you're doing, I
recommend manipulating the Expect channels only with the expect
commands.
Some effort was made to make Expect support threads, however it is not
complete. You can compile Expect with threads enabled but don't run
Expect in multiple threads just yet.
So much code has changed, there are bound to be bugs in dark corners.
Please let me know of such cases. The best response will come by
supplying a simple test case that can be added to Expect's test suite.
In places where the behavior of Expect was not precisely documented,
full advantage was taken to do something different :-)
Several esoteric bugs were fixed.
Although Expect itself uses Henry Spencer's new regexp engine,
Expect's C library still uses his original regexp engine.
No testing has been done of the poll and non-event subsystems. (These
are used on systems which don't support select on ptys or ttys. Some
minor work needs to be done on them (because the event subsystem was
rewritten) which I'll probably do only if anyone requests it.
Many deprecated features (deprecated for many years!) have been
removed. All such features were deprecated prior to Exploring Expect
so if that's how you learned Expect, you have nothing to worry about.
For example, Expect's getpid command predates Tcl's pid command and
it's been deprecated for, oh.... 6 years - wow! Other deprecated features
include:
expect -timestamp (flag only; behavior itself was removed years ago)
expect -iwrite (flag only; behavior occurs all the time)
expect_version (use "exp_version" command)
expect_library (use "exp_library" global variable)
interact -eof (use "eof" keyword)
interact -timeout (use "timeout" keyword)
interact -timestamp (use "clock" command)
getpid (use "pid" command)
system stty (use "stty" command)
With this release, the following are deprecated:
timestamp (use "clock" command)
debugger (use a different one; there are very nice replacements
around. Fortunately the Expect debugger is not something anyone
is wiring into their scripts, so for now, consider it on the
endangered species list. Anyone still want this debugger?)
From now on, the most current snapshots of Expect will be found in the
Scriptics CVS repository. Not all snapshots are official releases.
For more, see the ChangeLog file in the expect distribution.
2000-09-05 18:20:29 +02:00
|
|
|
|
2007-12-11 22:40:42 +01:00
|
|
|
INSTALL_MAKE_FLAGS+= INSTALL_ROOT=${DESTDIR:Q}
|
|
|
|
|
|
2004-03-11 08:16:45 +01:00
|
|
|
.include "../../lang/tcl/buildlink3.mk"
|
Initial import of tcl-expect-5.32.1, the tcl half of the new expect packages.
Changes to the expect package since expect-5.25:
* This package is now split into two packages, tcl-expect, and
tk-expect. tcl-expect can be installed on systems without
X11 (and by extension, without tk).
* the copious expect examples and their man pages are now installed
into ${PREFIX}/share/examples/tcl/expect instead of into
${PREFIX}/bin and ${PREFIX}/man. If any of them are determined
to be worth separate use, they should be split out into a
separate package.
Changes to expect itself since expect-5.25:
** SUMMARY
Expect 5.31 now works with Tcl 8.2. Expect 5.31 does NOT work with
prior releases of Tcl. Thanks to an incredible amount of work by
Scott Stanton, Henry Spencer, Melissa Hirschl, and funding from
Scriptics for making this possible.
** NEW FEATURES
What? You mean that working with Tcl 8.2 isn't enough?????
Expect supports Tcl's new regexp engine.
Expect supports null bytes in strings directly. (You no longer have
to use the "null" keyword to send or match nulls. Of course, the
"null" keyword will continue to be supported.) Null removal (on
input) is still enabled by default since nulls are almost never
intended for end-user consumption in interactive dialogues.
** CHANGES IN BEHAVIOR (POTENTIAL INCOMPATIBILITIES)
The interpreter command used to exit upon eof. Now it uses "-eof
script" to control this behavior. The default behavior is to return.
(This change was required because Expect now gives control to Tcl upon
exit and Tcl waits (potentially forever) for all processes to die on
exit.) Explicit calls to interpreter are almost non-existent.
However, you should look for *implicit* calls via interact commands
with a pattern but no action. This required changes in the examples:
dislocate, dvorak, kibitz, and xkibitz.
Indirect variables can no longer start with "exp". Such variables
will be interpreted as channel names.
Old-style regexps may need conversion. If you have been protecting
regexps containing backslashes with {}, then you need to examine all
your backslashes since the new regexp engine interprets backslash
sequences (such as \n) itself. For example:
expect "\n" (works the same in Tcl 8.0 and 8.1)
expect {\n} (works differently in Tcl 8.0 and 8.1)
Scriptics has also created a new-regexp-features page which you should
read: http://www.scriptics.com/support/howto/regexp81.html. Some of
the new features allow much more efficient regexps than before. For
example, non-greedy quantifiers can replace [split] looping
constructions with a single regexp, enabling Tcl to parse very
efficiently. For the whole story, read the re_syntax man page.
The interact command's regexp matching no longer skips nulls. (I'd be
surprised if anyone misses this. At least I hope ....)
Expect's C library now reports failures in spawn's underlying exec
directly (by returning -1) rather than the way it used to (as data in
the pty). This makes user code more robust. However, it requires you
to simplify your code, alas. See the chesslib.c example.
Linking with Expect's C library no longer requires the Tcl library
(unless, of course, you make Tcl calls yourself). Tcl is still
required to build the library in the first place, however.
** CHANGES IN BEHAVIOR (SHOULD NOT CAUSE INCOMPATIBILITIES)
The match_max command now controls by bytes, not chars. This won't
cause problems unless your existing scripts are interacting using
sizeable chunks of multibyte characters. (If you don't know what I'm
talking about, ignore this.)
The Make/configure suite now corresponds to the TEA conventions (at
least in theory; the conventions are changing regularly so it's hard
to be less vague on this point). Significantly, this means that you
should be able to use the same configure flags as when compiling Tcl
or any other TEA-compatible extension. (See the INSTALL file.)
The values of special variables such as exp_spawn_id_any have changed.
(The values were never documented so you shouldn't have been using
them anyway.)
Spawn ids now appear as "exp...". (They used to be small integers.)
Do not assume that spawn ids will continue to be represented in any
particular way (other than unique strings).
** OTHER NOTES
Expect uses channels. There is an Expect channel type. It is
possible to use Tcl's channel commands, such as fconfigure, to change
the encoding. However, Expect layers its own buffering system on top
of Tcl's channel handler so don't expect intuitive behavior when using
commands such as gets and puts. Unless you know what you're doing, I
recommend manipulating the Expect channels only with the expect
commands.
Some effort was made to make Expect support threads, however it is not
complete. You can compile Expect with threads enabled but don't run
Expect in multiple threads just yet.
So much code has changed, there are bound to be bugs in dark corners.
Please let me know of such cases. The best response will come by
supplying a simple test case that can be added to Expect's test suite.
In places where the behavior of Expect was not precisely documented,
full advantage was taken to do something different :-)
Several esoteric bugs were fixed.
Although Expect itself uses Henry Spencer's new regexp engine,
Expect's C library still uses his original regexp engine.
No testing has been done of the poll and non-event subsystems. (These
are used on systems which don't support select on ptys or ttys. Some
minor work needs to be done on them (because the event subsystem was
rewritten) which I'll probably do only if anyone requests it.
Many deprecated features (deprecated for many years!) have been
removed. All such features were deprecated prior to Exploring Expect
so if that's how you learned Expect, you have nothing to worry about.
For example, Expect's getpid command predates Tcl's pid command and
it's been deprecated for, oh.... 6 years - wow! Other deprecated features
include:
expect -timestamp (flag only; behavior itself was removed years ago)
expect -iwrite (flag only; behavior occurs all the time)
expect_version (use "exp_version" command)
expect_library (use "exp_library" global variable)
interact -eof (use "eof" keyword)
interact -timeout (use "timeout" keyword)
interact -timestamp (use "clock" command)
getpid (use "pid" command)
system stty (use "stty" command)
With this release, the following are deprecated:
timestamp (use "clock" command)
debugger (use a different one; there are very nice replacements
around. Fortunately the Expect debugger is not something anyone
is wiring into their scripts, so for now, consider it on the
endangered species list. Anyone still want this debugger?)
From now on, the most current snapshots of Expect will be found in the
Scriptics CVS repository. Not all snapshots are official releases.
For more, see the ChangeLog file in the expect distribution.
2000-09-05 18:20:29 +02:00
|
|
|
.include "../../mk/bsd.pkg.mk"
|
