| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Bump PKGREVISION.
|
|
Our local patch for aczsh.m4, introduced to 5.0.2nb1:
http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/shells/zsh/Makefile#rev1.63
has been upstreamed. There is no longer a point to regen configure;
tiny patch to configure.ac can be directly applied to configure itself.
Bump revision.
|
|
Changelog:
5.9:
Changes since 5.8.1
-------------------
zsh 5.9 is dedicated to the memory of Sven Guckes, who was, amongst other
things, a long-time zsh advocate. For more information, see:
https://linuxnews.de/2022/02/sven-guckes-verstorben/
https://groups.google.com/g/vim_announce/c/MJBKVd-xrEE/m/joVNaDgAAgAJ
When unsetting a hash element, the string enclosed in square brackets is
interpreted literally after any normal command-line-argument expansions.
Thus
unset "hash[$key]"
first expands $key as usual for a double-quoted string, and then interprets
that result as the exact hash element to unset. This differs from previous
versions of the shell, which would also remove a leading backslash for an
unusual subset of characters in the expansion of $key. Note this also
means, for example, that now
unset 'hash[ab]cd]'
unsets the element with key "ab]cd" rather than silently doing nothing.
The function command learnt a -T option to declare a function and enable
tracing for it simultaneously.
The option SHORT_REPEAT was added to enable the short syntax of
SHORT_LOOPS for the repeat command only. It is disabled by default.
The _arguments function now supports NUL-delimiting optargs in the
opt_args array via the -0 option. Developers of completion functions
should find this easier to handle reliably than the default
colon-delimiting behaviour.
The zsh/system module's `zsystem flock` command learnt an -i option to
set the wait interval used with -t. Additionally, -t now supports
fractional seconds.
The option CLOBBER_EMPTY was added to enable the overwrite behaviour
of CLOBBER for empty files only. It is disabled by default.
A (-) expansion flag was added. It works like (n) but correctly sorts
negative numbers.
The (*) expansion flag enables EXTENDED_GLOB for pattern matching.
For example, ${(*)sample/(#b)*(pat)*/${match[1]}} uses backreferences
even if EXTENDED_GLOB is not otherwise set. However, this does not
descend into nested exapansions, and doubling as (**) does not disable
EXTENDED_GLOB.
The compinit function learnt a -w option to explain why compdump runs.
When run without the -i or -u options and compaudit discovers security
issues, answering "y" to the "Ignore insecure ..." prompt removes the
insecure elements (like the -i option) where previously it ignored the
result (thus formerly like the -u option). Further, removing those
elements includes dropping directories from the $fpath array.
The zsh/datetime module's strftime builtin learnt an -n option to omit
the trailing newline when printing a formatted time.
The XTRACE option is now disabled while running user-defined completion
widgets. This corresponds to long-standing behavior of other user ZLE
widgets. Use the _complete_debug widget to capture XTRACE output, or
use "functions -T" to enable tracing of specific completion functions.
The fc builtin learnt an -s option which is a POSIX equivalent to the
`fc -e-` method of re-executing a command without invoking an editor.
The option CASE_PATHS was added to control how NO_CASE_GLOB behaves.
NO_CASE_GLOB + NO_CASE_PATHS is equivalent to the current NO_CASE_GLOB
behaviour. NO_CASE_GLOB + CASE_PATHS treats only path components that
contain globbing characters as case-insensitive; this behaviour may
yield more predictable results on case-sensitive file systems.
NO_CASE_PATHS is the default.
With the new TYPESET_TO_UNSET option set, "typeset foo" leaves foo unset,
in contrast to the default behavior which assigns foo="". Any parameter
attributes such as numeric type, sorting, and padding are retained until
the parameter is explicitly unset or a conflicting value is assigned.
This is similar to default behavior of bash and ksh. This option is
disabled by default.
The compadd builtin's -D option can now be specified more than once.
The zsh/zutil module's zformat builtin learnt an -F option which behaves
like -f except that ternary expressions check for existence instead of
doing math evaluation.
The conventional syntax used to indicate units, ranges, and default values
in completion descriptions (e.g. `timeout (seconds) (0-60) [20]`) is now
recognised by the completion system itself. These components are parsed
out of the description and can be individually styled. A _numbers helper
function has been added to help function authors offer rich completion
for these values.
The log builtin, WATCH parameter, et al., have been broken out into a
separate module, zsh/watch. The module is enabled by default.
The zsh/watch module's WATCHFMT parameter now supports colours via the
%F and %K escapes.
The STTY parameter can now be set to an empty string before running a
command to automatically restore terminal settings after the command
finishes.
The "jobs" command and "$jobstates" and related parameters can report on
parent shell jobs even in subshells. This is a snapshot of the parent
state, frozen at the point the subshell started. However, if a subshell
starts its own background jobs, the parent state is discarded in order
to report on those new jobs.
|
|
Changes between 5.8 and 5.8.1
Incompatibilities
PROMPT_SUBST expansion is no longer performed on arguments to
prompt-expansion sequences such as %F.
Changes
CVE-2021-45444: Some prompt expansion sequences, such as %F,
support 'arguments' which are themselves expanded in case they
contain colour values, etc. This additional expansion would trigger
PROMPT_SUBST evaluation, if enabled. This could be abused to
execute code the user didn't expect. e.g., given a certain prompt
configuration, an attacker could trick a user into executing
arbitrary code by having them check out a Git branch with a
specially crafted name.
This is fixed in the shell itself by no longer performing
PROMPT_SUBST evaluation on these prompt-expansion arguments.
Users who are concerned about an exploit but unable to update their
binaries may apply the partial work-around described in the file
Etc/CVE-2021-45444-VCS_Info-workaround.patch included with the shell
source. [ Reported by RyotaK. Additional thanks to Marc Cornellà. ]
|
|
|
|
|
|
All checksums have been double-checked against existing RMD160 and
SHA512 hashes
|
|
|
|
Bump PKGREVISION.
TODO: _bsd_pkg should be usable for non-BSD platforms.
|
|
Bump PKGREVISION.
|
|
|
|
|
|
Changelog:
Changes between 5.7 and 5.8
Incompatibilities
The history expansion !:1:t2 used to be interpreted such that
the 2 was a separate character added after the history expansion.
Now it is an argument to the :t modifier. The behaviour of :h
has similarly changed.
The vcs_info function VCS_INFO_quilt-dirfind now returns a
string value by setting $REPLY. Previously it printed the value
to standard output.
The cd and chdir builtins no longer interpret operands like -1
and +2 as stack entries when POSIX_CD is enabled.
Dropping privileges with `unsetopt privileged` may fail (with
an error message) on some older and uncommon platforms due to
library dependency changes made in the course of fixing
CVE-2019-20044 (see below). Please report this to the zsh-workers
mailing list if your system is affected.
Changes
CVE-2019-20044: When unsetting the PRIVILEGED option, the shell
sets its effective user and group IDs to match their respective
real IDs. On some platforms (including Linux and macOS, but
not FreeBSD), when the RUID and EUID were both non-zero, it
was possible to regain the shell's former privileges by e.g.
assigning to the EUID or EGID parameter. In the course of
investigating this issue, it was also found that the setopt
built-in did not correctly report errors when unsetting the
option, which prevented users from handling them as the
documentation recommended. setopt now returns non-zero if it
is unable to safely drop privileges. [ Reported by Sam Foxman.]
The zsh/zutil module's zparseopts builtin learnt an -F option
to abort parsing when an unrecognised option-like parameter is
encountered.
The zsh/files module gained a chmod builtin.
Several changes have been made to the way completion functions
track 'precommands' (such as `command` and `env`) and determine
whether the command being completed for is a shell builtin.
Developers of completion functions may wish to familiarise
themselves with `_normal -p` and `_pick_variant -b`.
The option CD_SILENT was added to suppress all output from cd
(whether explicit or implicit with AUTO_CD). It is disabled by
default.
The compadd builtin's -o option now takes an optional argument
to specify the order of completion matches. This affects the
display of candidate matches and the order in which they are
selected when cycling between them using menu completion.
The :h and :t modifiers in parameter expansion (if braces are
present), glob qualifiers and history expansion may take
following decimal digit arguments in order to keep that many
leading or trailing path components instead of the defaults of
all but one (:h) and one (:t). In an absolute path the leading
'/' counts as one component.
The functions builtin gained a -c option to efficiently copy
functions.
The zshmisc(1) manual page incorrectly stated that when 'exit'
is used in a `try' block inside a function, the corresponding
`always' block will be executed. The manual page has been
corrected. The shell's behaviour has not changed.
|
|
pkglint --only "https instead of http" -r -F
With manual adjustments afterwards since pkglint 19.4.4 fixed a few
indentations in unrelated lines.
This mainly affects projects hosted at SourceForce, as well as
freedesktop.org, CTAN and GNU.
|
|
pkglint -Wall -F --only aligned --only indent -r
No manual corrections.
|
|
Bump PKGREVISION.
|
|
|
|
* Move --enable-zsh-mem configure option to non-debug part
to stabilize zsh with NetBSD's new jemalloc
Changelog:
2019-02-03 dana <dana@dana.is>
* unposted: Config/version.mk, Etc/FAQ.yo, README: Update for
5.7.1
* 44034: Completion/Unix/Type/_date_formats: Complete %9./%N,
adjust some wording
* 44033: Completion/Unix/Command/_dos2unix: Add completion for
dos2unix/unix2dos
* 44030: Src/prompt.c, Test/D01prompt.ztst: Return error for
unrecognised colour name
2019-01-28 Fredric Silberberg <fred@silberberg.xyz>
* github #32: Completion/Unix/Command/_git: Fix a typo in the
git tag completion.
2018-01-27 dana <dana@dana.is>
* unposted: Etc/creating-a-release.txt: Document additional
release steps
* 44020: Functions/VCS_Info/Backends/VCS_INFO_detect_p4: Fix
infinite recursion
|
|
This makes zsh much more stable on -current for me.
|
|
Upstream changes:
2019-01-24 : Release 5.7
Bug fix release with a few user visible additions.
2018-01-24 dana <dana@dana.is>
* unposted: Config/version.mk, README: Update for 5.7
2018-01-23 dana <dana@dana.is>
* 44012: Test/X04zlehighlight.ztst: Fix spurious test failures
on OpenBSD
2019-01-23 Mikael Magnusson <mikachu@gmail.com>
* 44011: Doc/Zsh/zle.yo, Src/prompt.c, Test/X04zlehighlight.ztst:
Only use fg_start_code for non-truecolor
|
|
|
|
|
|
Upstream changes:
Changes from 5.6.1 to 5.6.2
---------------------------
Fix another SIGTTOU case.
Fix SIGWINCH being ignored when zsh is not in the foreground.
The release tarballs are now compressed using xz(1), whereas previously
both xz(1) and gzip(1) versions were available. If this gets in your way,
give us a shout.
|
|
Changelog:
Changes from 5.6 to 5.6.1
-------------------------
Fix packaging issue that broke runhelp.
Fix a regression with pipelines getting backgrounded and emitting SIGTTOU.
|
|
Upstream changes:
Changes from 5.5.1-test-2 to 5.6
--------------------------------
CVE-2018-0502: Data from the second line of a #! script file might be passed to
execve(). For example, in the following situation -
.
printf '#!foo\nbar' > baz
./baz
.
the shell might take "bar" rather than "foo" for the argv[0] to be passed to
execve(). [ Reported by Anthony Sottile and Buck Evan. ]
CVE-2018-13259: A shebang line longer than 64 characters would be truncated.
For example, in the following situation:
.
( printf '#!'; repeat 64 printf 'x'; printf 'y' ) > foo
./foo
.
the shell might execute x...x (64 repetitions) rather than x...xy (64 x's,
one y). [ Reported by Daniel Shahaf. ]
Changes from 5.5.1 to 5.5.1-test-2
----------------------------------
Non-stop IEEE 754 arithmetic support - Inf and NaN are now returned
from floating point operations where errors were printed before.
Inf and NaN are also recognised in arithmetic expressions.
In shell patterns, [[:blank:]] now honours the locale instead of
matching exclusively on space and tab, like for the other POSIX
character classes or for extended regular expressions.
Nanosecond precision on file times is supported in the module
zsh/stat.
|
|
Changelog:
Changes from %.5 to 5.5.1
-------------------------
Apart from a fix for a configuration problem finding singal names from
(some) recent versions of glibc, there are only minor changes.
Changes from 5.4.2 to 5.5
-------------------------
The effect of the NO_INTERACTIVE_COMMENTS option extends into $(...) and
`...` command substitutions when used on the command line. Previously,
comments were always recognized within command substitutions unless the
comment character "#" was disabled via reset of $histchars.
An alternative assignment syntax for indicating indices for arrays
and keys for associative arrays:
typeset -a array=([1]=first [2]=second)
typeset -A assoc=([key1]=val1 [key2]=val2)
is allowed for compatibility with other shells. In the case of normal
arrays the new syntax can be mixed with the old.
|
|
and CVE-2018-7549 from the zsh repo. one pullup less, w00t. :-P
|
|
This change makes shells/zsh build on Ubuntu Linux.
|
|
pkgsrc changes:
- Use PRINT_PLIST_AWK to aid future upgrades.
- Support the "static" option on Darwin and SunOS.
Upstream changes from 5.3.1 to 5.4:
The 'exec' and 'command' precommand modifiers, and options to them, are
now parsed after parameter expansion. Previously, both the modifier and
any options to it were parsed between alias expansion and parameter
expansion (see zshexpn(1)), so they could neither be quoted nor be the
result of parameter expansion. Examples: 's=command; $s -V ls' and
'\command -V ls' now work as expected.
Functions executed by ZLE widgets no longer have their standard input
closed, but redirected from /dev/null instead. That still guards
against user defined widgets inadvertently reading from the tty device.
There is an option WARN_NESTED_VAR, a companion to the existing
WARN_CREATE_GLOBAL that causes a warning if a function updates a
variable from an enclosing scope without using typeset -g. It can be
turned on for an individual function with "functions -W".
zmodload now has an option -s to be silent on a failure to find a module
but still print other errors.
|
|
configure script fails to autodetect when running in a pbulk environment.
|
|
|
|
- Get rid of useless Makefile.common and pointless variables since there is
no longer a zsh-current package.
- Remove non-standard per-OS non-checksummed patch file in FILESDIR.
Integrate it correctly in the normal way.
- Ensure our patched configure.ac is actually regenerated.
- Use REPLACE_INTERPRETER instead of homegrown subst replacements.
- Remove esoteric and fragile configuration variables, a bunch of legacy OS
based options, and simply depend correctly on terminfo and curses.
- Remove custom test targets and requirements for root access, the test suite
works fine as a non-root user and can be done in the normal way.
- Use options.mk
- Set maintainer to pkgsrc-users, uebayasi resigned.
Fixes build on at least SunOS. Tested on SunOS, Darwin, NetBSD (with and
without the "static" option), and Linux.
|
|
|
|
---------------------------
2016-12-21 Peter Stephenson <p.w.stephenson@ntlworld.com>
* unposted: Config/version.mk, Etc/FAQ.yo, NEWS, README:
release 5.3.1:
2016-12-18 Baptiste Daroussin <bapt@FreeBSD.org>
* 40210: Completion/Unix/Command/_sysctl: Add support modern
FreeBSD and drop support for FreeBSD < 5
2016-12-18 Baptiste Daroussin <bapt@gandi.net>
* 40209: Completion/BSD/Command/_chflags: Fix typo in chflags
completion
2016-12-16 Daniel Shahaf <d.s@daniel.shahaf.name>
* 40149: Functions/VCS_Info/Backends/VCS_INFO_get_data_git:
vcs_info git: Avoid a fork.
* 40203: Test/B03print.ztst: Resolve 'printf --' question from
grandparent commit (thanks Chet).
2016-12-15 Barton E. Schaefer <schaefer@zsh.org>
* 40198: Test/V10private.ztst: output of B02typeset differs when
(( UID == 0 )) so do not attempt to redo that test in that case
2016-12-14 Barton E. Schaefer <schaefer@zsh.org>
* 40179: Src/builtin.c: fix handling of "printf -" and "printf --"
* unposted: Test/B03print.ztst: regression for 40179 / 37467
2016-12-12 Peter Stephenson <p.w.stephenson@ntlworld.com>
* unposted: Config/version.mk: update to 5.3-dev-0 to avoid
clash with installed 5.3.
|
|
|
|
Changelog:
Changes from 5.2 to 5.3
-----------------------
It is possible to enable character width support for Unicode 9 by
configuring with `--enable-unicode9'; this compiles in some additional
tables. At some point this support may move into a module, in which
case the configure option will be changed to cause the module to be
permanently loaded. This option is not useful unless your terminal also
supports Unicode 9.
The new word modifier ':P' computes the physical path of the argument.
It is different from the existing ':a' modifier which always resolves
'/before/here/../after' to '/before/after', and differs from the
existing ':A' modifier which resolves symlinks only after 'here/..' is
removed, even when /before/here is itself a symbolic link. It is
recommended to review uses of ':A' and, if appropriate, convert them
to ':P' as soon as compatibility with 5.2 is no longer a requirement.
The output of "typeset -p" uses "export" commands or the "-g" option
for parameters that are not local to the current scope. Previously,
all output was in the form of "typeset" commands, never using "-g".
vi-repeat-change can repeat user-defined widgets if the widget calls
zle -f vichange.
The parameter $registers now makes the contents of vi register buffers
available to user-defined widgets.
New vi-up-case and vi-down-case builtin widgets bound to gU/gu (or U/u
in visual mode) for doing case conversion.
A new select-word-match function provides vim-style text objects with
configurable word boundaries using the existing match-words-by-style
mechanism.
Support for the conditional expression [[ -v var ]] to test if a
variable is set for compatibility with other shells.
The print and printf builtins have a new option -v to assign the output
to a variable. This is for bash compatibility but with the additional
feature that, for an array, a separate element is used each time the
format is reused.
New x: syntax in completion match specifications make it possible to
disable match specifications hardcoded in completion functions.
|
|
|
|
|
|
NEWS:
Changes from 5.1.1 to 5.2
-------------------------
The new module zsh/param/private can be loaded to allow the shell
to define parameters that are private to a function scope (i.e. are
not propagated to nested functions called within this function).
The parameter flag ${(P)...} is now more useful when it appears in
a nested expansion. For example,
typeset -A assoc=(one un two deux three trois)
name=assoc
print ${${(P)name}[one]}
now prints "un". In previous versions of the shell the value of the
substitution was fully expanded on return from ${(P)name}, making
associative array subscripting difficult. As a side effect, flags
for formatting appearing in the inner substitution now affect the
substitution of the name (into "assoc" in this case), which is not
normally useful: flags that should apply to the value must be in the
outer substitution.
The GLOB_STAR_SHORT option allows the pattern **/* to be shortened to
just ** if no / follows. so **.c searches recursively for a file whose
name has the suffix ".c".
The effect of the WARN_CREATE_GLOBAL option has been significantly
extended, so expect it to cause additional warning messages about
parameters created globally within function scope.
README:
Incompatibilities between 5.1 and 5.2
-------------------------------------
The behaviour of the parameter flag (P) has changed when it appears
in a nested parameter group, in order to make it more useful in
such cases. A (P) in the outermost parameter group behaves as
before. See NEWS for more.
|
|
Changelog:
Changes from 5.1 to 5.1.1
-------------------------
5.1.1 is primarily a bug fix release; however, a few minor features were
added.
The ZLE variables YANK_ACTIVE, YANK_START and YANK_END have been added
and are useful for managing highlighting.
The zsh-specific pattern match range tests have been supplemented with
[:INCOMPLETE:] and [:INVALID:] to help detect the state of partially
read multibyte character strings.
|
|
settings of INSTALL_UNSTRIPPED=yes for Darwin in individual packages.
|
|
|
|
pkgsrc changes:
removed patch:
patch-Completion_Unix_Command__du
patch-Completion_Unix_Command__sort
patch-Src_builtin.c
patch-Test_B03print.ztst
quote from zsh-5.1/ChangeLog:
* 36120: Completion/Unix/Command/_sort: Fix syntax error
* 35467: Completion/Unix/Command/_du: complete files for non-GNU du
* 35412: Src/builtin.c, Test/B03print.ztst: fix for - flag
when formating strings with printf that was broken in 34841
separate a patch ( $ mv patches/patch-ac files/patch-ac )
zsh-5.1/NEWS:
Changes from 5.0.8 to 5.1
-------------------------
The builtins declare, export, local, readonly and typeset
now have corresponding reserved words. When used in
this form, the builtin syntax is extended so that assignments
following the reserved word are treated similarly to
assignments that appear at the start of the command line.
For example,
local scalar=`echo one word` array=(several words)
creates a local "scalar" containing the text "one word"
and an array "array" containing the words "several"
"words".
- The print builtin has new options -x and -X to expand tabs.
- Several new command completions and numerous updates to others.
- Options to "fc" to segregate internal and shared history.
- All emulations including "sh" use multibyte by default; several
repairs to multibyte handling.
- ZLE supports "bracketed paste" mode to avoid interpreting pasted
newlines as accept-line. Pastes can be highlighted for visibility
and to make it more obvious whether accept-line has occurred.
- Improved (though still not perfect) POSIX compatibility for getopts
builtin when POSIX_BUILTINS is set.
- New setopt APPEND_CREATE for POSIX-compatible NO_CLOBBER behavior.
- Completion of date values now displays in a calendar format when
the complist module is available. Controllable by zstyle.
- New parameter UNDO_LIMIT_NO for more control over ZLE undo repeat.
- Several repairs/improvements to the contributed narrow-to-region
ZLE function.
- Many changes to child-process and signal handling to eliminate race
conditions and avoid deadlocks on descriptor and memory management.
- New builtin sysopen in zsh/system module for detailed control of
file descriptor modes.
zsh-5.1/README:
Incompatibilites between 5.0.8 and 5.1
--------------------------------------
The default behaviour when text is pasted into an X Windows terminal has
changed significantly (unless you are using a very old terminal emulator
that doesn't support this mode). Now, the new "bracketed paste mode"
treats all the pasted text as literal characters. This means, in
particular, that a newline is simply inserted as a visible newline; you
need to hit Return on the keyboard to execute the pasted text in one go.
See the description of zle_bracketed_paste in the zshparams manual for
more. "unset zle_bracketed_paste" restores the previous behaviour.
As noted in NEWS, the builtins declare, export, float, integer, local,
readonly and typeset now have corresponding reserved words that provide
true assignment semantics instead of an approximation by means of normal
command line arguments. It is hoped that this additional consistency
provides a more natural interface. However, compatbility with older
versions of zsh can be obtained by turning off the reserved word
interface, exposing the builtin interface:
disable -r declare export float integer local readonly typeset
This is also necessary in the unusual eventuality that the builtins are
to be overridden by shell functions, since reserved words take
precedence over functions.
|
|
might incur ncurses dependencies on some platforms, and ncurses just bumped
its shlib.
Some packages were bumped twice now, sorry for that.
|
|
- non-GNU du wouldn't complete filenames (taken from upstream)
- sort completion threw a syntax error on NetBSD (reported upstream)
Bump PKGREVISION to 1.
|
|
* Include bugfix,
https://sourceforge.net/p/zsh/code/ci/ac26fafa03c30e8c79e4bd70bdbb68d025643ee7/
Changelog:
Changes from 5.0.7 to 5.0.8
---------------------------
- Global aliases can be created for syntactic tokens such as command
separators (";", "&", "|", "&&", "||"), redirection operators, etc.
Use at your own risk! The POSIX_ALIASES option is interpreted more
strictly to prevent expansion of these and other alias names containing
quotes, glob metacharacters, parameter references, etc.
- There have been various further improvements to builtin handling
with the POSIX_BUILTINS option (off by default) for compatibility with
the POSIX standard.
- 'whence -v' is now more informative, and 'whence -S' shows you
how a full chain of symbolic links resolves to a command.
- The 'p' parameter flag now allows an argument to be specified
as a reference to a variable, e.g. ${(ps.$sep.)foo} to split $foo
on a string given by $sep.
- The option FORCE_FLOAT now forces variables, not just constants,
to floating point in arithmetic expressions.
- The type of an assignment in arithmetic expressions, e.g. the
type seen by the variable res in $(( res = a = b )), is now
more logical and C-like.
- The default binding of 'u' in vi command mode has changed to undo
multiple changes when invoked repeatedly. '^R' is now bound to redo
changes. To revert to toggling of the last edit use:
bindkey -a u vi-undo-change
- Compatibility with Vim has been improved for vi editing mode. Most
notably, Vim style text objects are supported and the region can be
manipulated with vi commands in the same manner as Vim's visual mode.
- Elements of the watch variable may now be patterns.
- The logic for retrying history locking has been improved.
- Some rationalisations have been made to the zsh/db/gdbm module that
should make it more useful and predictable in operation.
|
|
|
|
|
|
Thix fixes, at the very least, issues with cvs command/filename
completion.
Bump PKGREVISION to 1.
|
|
|
