Note that this was the intended fix in PORTREVISION 3, the previous
commit, and was the change intended by ports/161999.
PR: ports/161999
Submitted by: Eugene Paskevich <eugene@raptor.kiev.ua>
had both lines:
Author: ...
WWW: ....
So standardize on that, and move them to the end of the file when necessary.
Also fix some more whitespace, and remove more "signature tags" of varying
forms, like -- name, etc.
s/AUTHOR/Author/
A few other various formatting issues
- Name
em@i.l
or variations thereof. While I'm here also fix some whitespace and other
formatting errors, including moving WWW: to the last line in the file.
bash completion should just work when you install new commands. Bash::Completion
is a system to use and write bash completion rules.
For end-users, you just need to add this line to your .bashrc or .bash_profile:
setup-bash-complete
This will load all the installed Bash::Completion plugins, make sure they should
be activated and generate the proper bash code to setup bash completion for
them.
If you later install a new command line tool, and it has a
Bash::Completion::Plugin -based plugin, all your new shells will have bash
completion rules for it. You can also force immediate setup by running the same
command:
setup-bash-complete
To write a new Bash::Completion plugin, see Bash::Completion::Plugin.
WWW: http://search.cpan.org/dist/Bash-Completion/
hostnames OR commands. First and foremost Ambit is meant to be a general
purpose hostlist enumerator to be used by other applications or scripts.
Additionally Ambit can be used to manage User Specific as well as
System-Wide HostGroups. It can also be used to query Network HostGroups.
Finally, Ambit is able to detect when it is expanding a command (rather than
a host list), allowing for the command to be expanded and executed
synchronously. This means Ambit can expand and run just about anything on
the command line and usually works in places where Bash Brace Expansion
might fail.
WWW: http://m.a.tt/er/ambit/
PR: 159769
Submitted by: Sascha Klauder <sklauder@trimind.de>
Approved by: sahil (mentor)
Under certain circumstances, running `fc -l' two times in succession
with a relative history offset at the end of the history will result
in an incorrect calculation of the last history entry and a seg fault
PR: 160239
2011-05-01 irc/gdesklets-irc: Upstream disapear and distfile is no more available
2011-06-24 net/libevnet: no longer necessary now that libevent2 has been released
2011-05-01 shells/44bsd-csh: Upstream disapear and distfile is no more available
2011-05-01 www/mod_auth_ldap: apache 13/20 is sceduled for deletion, migrate to 2.2.x+ and mod_authnz_ldap now
2011-05-01 www/mod_auth_remote: will be unsupported by ASF when 2.4.0 is release, migrate to 2.2.x+ now
2011-05-01 www/mod_authenticache: will be unsupported by ASF when 2.4.0 is release, migrate to 2.2.x+ now
2011-05-01 www/mod_layout2: will be unsupported by ASF when 2.4.0 is release, migrate to 2.2.x+ now
2011-05-01 www/mod_macro2: will be unsupported by ASF when 2.4.0 is release, migrate to 2.2.x+ now
2011-05-01 www/mod_traf_thief: will be unsupported by ASF when 2.4.0 is release, migrate to 2.2.x+ now
2011-05-01 www/mod_transform: will be unsupported by ASF when 2.4.0 is release, migrate to 2.2.x+ now
-Update to May 26, 2011 snapshot:
Add support for OpenSSH's sftp-server umask option.
Remove inline references to satisify certain compilers
Remove the now unnecessary sftp-logging compatibility mode.
When getopt_long is not available, like on AIX, use bundled NetBSD
getopt_long.
Update the SECURITY document to include a reference to /etc/popt and \
~/.popt as they relate to rsync.
Fix for rsync-3.0 which now uses a short -e option, with an optional
argument as a server side option indicating protocol compatibility.
Fix scponly crash on Solaris
Fix detection and inclusion of getopt on certain platforms
Document risks associated with popt reading /etc/popt and ~/.popt
Document getopt requirement (when certain configure options are enabled)
- cleanup redundant BUILD_DEPENDS+= [1]
PR: ports/157804
Submitted by: Rob Farmer <rfarmer _at_ predatorlabs.net> (maintainer), ohauer [1]
Approved by: maintainer
Changes since 4.3.11
--------------------
The zsh/parameter module has a new readonly associative array
$usergroups whose keys are the names of system groups of which the
current user is a member and whose values are the corresponding
group identifiers.
The region_highlight array, which controls highlighting of the
command line from zle widgets, is now updated dynamically as
the command line is edited.
In POSIX emulation ("emulate sh") the shell is more accurate about
when it should or should not exit on errors.
The ${NAME:OFFSET:LENGTH} syntax now supports negative LENGTH, which
counts back from the end of the string.
The (g:opts:) flag in parameter expansion processes escape sequences like
the echo and print builtins. opts can be any combination of o, e and c.
With e, acts like print rather than echo except for octal escapes which
are controlled separately by the o option. With c, interpret control
sequences like "^X" as bindkey does. Regardless of the opts, \c is not
interpreted.
2011-05-01 audio/albumart: Upstream disapear and distfile is no more available
2011-05-01 audio/aylet: Upstream disapear and distfile is no more available
2011-05-01 audio/cantus: Upstream disapear and distfile is no more available
2011-05-01 audio/xaylet: Upstream disapear and distfile is no more available
2011-05-01 science/oases: Upstream disapear and distfile is no more available
2011-05-01 shells/pash: Upstream disapear and distfile is no more available
If a ports is linked against ncurses from base or from the ports, it should then add:
USE_NCURSES=yes
it is also possible to specify the hard dependency on the ports ncurses or one the base one adding the following macros:
WITH_NCURSES_PORT=yes or WITH_NCURSES_BASE=yes
PR: ports/155269
Submitted by: me
Reviwed by: pav@
Approved by: portmgr (pav@)
Exp-run by: portmgr (pav@)
According to the CHANGES file, the avahi-browse error is patched in this
version, though in a manner a bit different from our patch. Please test
on amd64 and let me know if the problem has regressed.
2011-01-24 dns/staticcharge: abandoned by author
2011-01-21 shells/bash3-static: Use shells/bash or shells/bash-static instead
shells/bash3 is still used by devel/quilt
Feature safe: yes
-Drop long comment describing knobs - it just duplicates OPTIONS
-For SCPONLY_DEFAULT_CHDIR, print a note about setting it. I'm not sure if post-patch is the best place for this, though?
-Drop dead site and just use Sourceforge
-Use the PORTDOCS variable
-Install some useful docs and drop useless one (TODO)
-Drop pre-everything message about defaults changing; that was 5 years ago
-LOCALBASE vs. PREFIX correction
-Add post-install messages to the plist so package users see them too
PR: ports/153115
Submitted by: Rob Farmer <rfarmer@predatorlabs.net> (maintainer)
Rsync 3 needs the "-e" option, which is blocked without this patch by scponly
Patch pulled from upstream CVS, which states a full release will come soon:
http://lists.ccs.neu.edu/pipermail/scponly/2010-November/002170.html
Reported by: Frank Bartels <knarf _at_ knarf.de>
PR: 152869
Submitted by: Rob Farmer <rfarmer _at_ predatorlabs.net> (maintainer)
completions. Tons of thanks to Raphael Kubo da Costa for identifying the
fix and providing us with a patch, and to ehaupt for testing!
PR: ports/150322
Submitted by: Raphael Kubo da Costa <kubito@gmail.com>
Reviewed by: ehaupt
shells/bash-completion is developed by a new group and has some very nice new
features. Unfortunately, the new version currently causes problems on amd64
systems. People with amd64 systems may use this classic version as an
alternative.
conflict with it. Also, remove the rsync-disable hack on amd64, and
replace it with a simple BROKEN message.
Note that shells/bash-completion-classic is currently an unedited
repocopy, but I know ehaupt is working to get it up and running.
The previous bash-completion package hadn't been updated since 2006. A
new group has picked up the package and continued development. The old
completions should remain, so I'm not going to update UPDATING.
I'm taking maintainership of this as well. Many thanks to Kirk, the
previous maintainer!
