Add new option BASE_ZSH that makes zsh and rzsh also available as
/bin/zsh and /bin/rzsh.
Under ports flamework everything is installed under /usr/local unless
custom prefix is used. And according to it zsh is installed as
/usr/local/bin/zsh. But on most Linux based OSes zsh is installed as
/bin/zsh. And it causes problem if user's account information is
shared between FreeBSD and Linux by using such tools as LDAP or NIS as
account information also includes absolute path of user's login shell.
To work around it I have created /bin/zsh as symbolic link referencing
/usr/local/bin/zsh and also edited /etc/shells to add /bin/zsh to it
every time I set up new FreeBSD system. But it's quite bothersome and
that is why I add new BASE_ZSH option.
While I'm here,
* Pet portclippy
* Re-format Makefile with portfmt
PR: 259109
Proposed by: Chris Hutchinson (more intuitive option name)
Approved by: maintainer timeout (> 2 weeks)
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Approved by: portmgr (blanket)
A command-line shell that focuses on productivity and swiftness featuring:
- A POSIX compliant interactive shell with some Bash extensions.
- Tab completions and syntax highlighting.
- Bash completion support (by internally invoking the genuine Bash).
- Builtin zero configration features.
- Written in Rust 🦀
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Many CONFLICTS definitions used patterns like "bash-[0-9]*" to filter
for the bash package in any version. But that pattern is functionally
identical with just "bash".
Approved by: portmgr (blanket)
bash actually only requires libtinfo, but up to recent change in
14.0-CURRENT, libtinfo and libncurses were bundled into one single libs,
so linking only to libncurses was not a problem.
By telling bash to link to libtinfo and not to libncurses, it works on
both system where ncurses has been split and those without the split as
there is a libtinfow.so symlink to libncursesw.so on those.
in preparation for the split in base of libtinfo and libncurses, clearly
specify when the packages should link against.
Note this also fixes the build with ports ncurses
- Update to the latest version 2.22 and fix manpage installation
- Reformat port description for better looks, add one missing slash
and one Oxford comma while I'm here
PR: 258277
Many consecutive timeouts. We thank smatsui for all his efforts and
hope to see him back in the future.
PR: 255256
PR: 255257
PR: 255258 [1]
Approved by: maintainer timeout (smatsui@karashi.org, > 2 months), dbaio (mentor)
Approved by: portmgr (adamw) [1]
Differential Revision: https://reviews.freebsd.org/D30769 [1]
