| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
| |
Tarsnap now ships with a zsh completion script.
Please use the completion from sysutils/tarsnap instead of this port.
Reported by: cperciva
|
|
|
|
|
| |
MFH: 2022Q1
Security: CVE-2021-45444
|
|
|
|
| |
Reported by: portscout
|
| |
|
|
|
|
|
| |
PR: 261449
Security: ee26f513-826e-11ec-8be6-d4c9ef517024
|
|
|
|
| |
PR: 261327
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The authors removed the shell functionality but it is still a good dev-tool.
Changelog
---------
* Added support for Scala 2.13.8
* Re-added old Main entry point for better compatibility with Ammonite 2.4 and
older
* Dropped built-in support for shell operations
* move from shells/ammonite to devel/ammonite
PR: 261191
Reported by: freebsd-ports@jan0sch.de (maintainer)
|
| |
|
|
|
|
| |
Reported by: ler@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There have been lots of missing CONFLICTS_INSTALL entries, either
because conflicting ports were added without updating existing ports,
due to name changes of generated packages, due to mis-understanding
the format and semantics of the conflicts entries, or just due to
typoes in package names.
This patch is the result of a comparison of all files contained in
the official packages with each other. This comparison was based on
packages built with default options and may therefore have missed
further conflicts with optionally installed files.
Where possible, version numbers in conflicts entries have been
generalized, some times taking advantage of the fact that a port
cannot conflict with itself (due to logic in bsd.port.mk that
supresses the pattern match result in that case).
A few ports that set the conflicts variables depending on complex
conditions (e.g. port options), have been left unmodified, despite
probably containing outdated package names.
These changes should only affect the installation of locally built
ports, not the package building with poudriere. They should give an
early indication of the install conflict in cases where currently
the pkg command aborts an installation when it detects that an
existing file would be overwritten,
Approved by: portmgr (implicit)
|
| |
|
| |
|
|
|
|
| |
Reported by: portscout
|
|
|
|
|
|
|
| |
Changelog: https://elv.sh/blog/0.17.0-release-notes.html
PR: 260621
Reported by: Adam Jimerson <vendion@gmail.com> (maintainer)
|
| |
|
|
|
|
| |
Reported by: ler
|
|
|
|
| |
PR: 260378
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit ae1787aab23e44e369dbb0cc814e8318c6f86e0d.
Requested by: maintainer
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
| |
PR: 259932
|
| |
|
| |
|
|
|
|
| |
Approved by: maintainer
|
|
|
|
|
|
|
|
|
| |
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 :crab:
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
| |
PR: 256581
|
|
|
|
| |
Approved by: portmgr (blanket)
|
|
|
|
| |
Approved by: portmgr (blanket)
|
| |
|
| |
|
|
|
|
| |
Approved by: portmgr (blanket)
|
|
|
|
|
|
| |
- Add a static flavor and install in /rescue same as editors/mg@static
Changes: https://github.com/ibara/oksh/releases/tag/oksh-7.0
|
|
|
|
|
|
| |
/bin/sh: Syntax error: Unterminated quoted string
Reported by: pkg-fallout
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
|
|
| |
ChangeLog: https://elv.sh/blog/0.16.0-release-notes.html
PR: 258415
Reported by: vendion@gmail.com (maintainer)
|
| |
|