disabled.
This allows users to avoid mounting an extra FS that we don't enable by default.
Only display pkg-message with fdescfs instructions when option is enabled.
Submitted by: swills
Differential Revision: https://reviews.freebsd.org/D10394
Changelog:
- Faster disk scanning on Windows and Unix and on OS/2 with Watcom C
built version.
This was achieved by removing the DOSDIR directory interface
layer and replacing it with system specific functions.
Disk scanning speed depends on external factors, like disk
caching and other processes accessing the disk at the same time.
The speed increasement you experience may vary.
- Fixed -rmtree for unicode file names on Windows.
- Support EMX symbolic links on OS/2.
- Support bash on OS/2.
- New Danish translation of the messages. Thanks to Joe Hansen.
with the real value of LOCALBASE by the port Makefile at some point, but it
isn't at the moment.
Set this value in the Makefile by defining CPPFLAGS accordingly.
PR: 217451
Submitted by: Dan McGregor <dan.mcgregor@usask.ca>
MFH: 2017Q1 (blanket)
The mistake was completely on my part, I somehow connected the dots the
wrong way in my head.
The only exceptions (for now) are archivers/zstd and ports-mgmt/synth
which were already picked up by new volunteers in the mean time.
(e.g. systems with an encrypted root partition) where it is impossible for the
fdescfs module to be autoloaded when /boot/kernel isn't available yet. Change
pkg-message accordingly.
Also change 'fdesc' mount point name to 'fdescfs' to simplify things: this way
'mount fdescfs' will work just as fine as 'umount fdescfs'. The less things to
remember - the better it is.
PR: 216985
Submitted by: John Smith <godevilove@ya.ru>
Eliminate errors during command completion for python, python2, and python3 if
the /usr/local/bin/python symlink does not exist. Additionally, even if the
symlink does exist, the completions will be wrong for the non-default
interpreter. So I'm simply deleting the problematic completions altogether. I
opened an upstream bug for the latter issue.
https://github.com/fish-shell/fish-shell/issues/3840
While I'm here, delete an extraneous patch file for DOCS=off
PR: 216987
Reported by: Keren Sky <keren_sky@live.com>
Approved by: brd (ports, implicit)
The ksh93 build process requires the pre-GCC5 CPP newline behavior, which
the -P argument provides by disabling line markers. This enables ksh93
to be built by gcc5 and later.
Approved by: GCC blanket
PR: 216707 (related)
- pass maintainership to submitter
- switch to github
- add NO_ARCH, update project web-page and remove unneded patch
This release fixing some vulnerabilities, that defeats the purpose
of the package entirely, so this is why MFH is requested.
PR: 215989
Submitted by: Damien Fleuriot <dam@my.gd>
MFH: 2017Q1
Changelog:
Fixes a bug. When -N is used, the input is not supposed to be split
using $IFS, but leading and trailing IFS whitespace was still removed.
MFH: 2017Q1
Changelog:
Under certain circumstances, bash will evaluate arithmetic expressions as
part of reading an expression token even when evaluation is suppressed. This
happens while evaluating a conditional expression and skipping over the
failed branch of the expression.
There is a race condition in add_history() that can be triggered by a fatal
signal arriving between the time the history length is updated and the time
the history list update is completed. A later attempt to reference an
invalid history entry can cause a crash.
Depending on compiler optimizations and behavior, the `read' builtin may not
save partial input when a timeout occurs.
Subshells begun to run command and process substitutions may attempt to
set the terminal's process group to an incorrect value if they receive
a fatal signal. This depends on the behavior of the process that starts
the shell.
MFH: 2017Q1
Changelog:
- Out-of-range negative offsets to popd can cause the shell to crash attempting
to free an invalid memory block.
- When performing filename completion, bash dequotes the directory name being
completed, which can result in match failures and potential unwanted
expansion.
MFH: 2017Q1
locale set by the user. Add LANG=C and LC_ALL=C at the beginning of
bsd.port.mk and export them so all commands are executed with the C locale.
LC_ALL=C overrides all other LC_* variables. LANG is used by setlocale(3)
as default value for LC_* variables, so normally it isn't used when LC_ALL
is set, but there's code out there that looks at LANG directly so it's safer
to set it as well. The only commands not captured by this are !=
assignments before any inclusion of bsd.port.*mk.
Introduce USE_LOCALE=<locale> that adds LANG=<locale> and LC_ALL=<locale> to
CONFIGURE_ENV and MAKE_ENV so upstream build systems can be executed with a
different locale (e.g. USE_LOCALE=en_US.UTF-8).
PR: 215882
Exp-run by: antoine
Approved by: portmgr (antoine)
The gcc6-aux port doesn't build libssp* to which the stack-protctor switch
could try to link. I believe the bdb generator was linking with the base
ssp libraries. The linker couldn't find the base ssp libraries on
DragonFly, which revealed the issue.
SPARforte is an open source programming language for high-integrity tasks,
efficient development over the project lifecycle and assuming best practices.
Language characteristics:
* Paradigm: imperative/ procedural, scripting, shell, limited reflexive
* Typing Disciplines: strong typing, type safety, nominative static with
optional limited weak and duck typing
* Appeared: 2001 (Ken O. Burtch)
* Source Code: GCC Ada, GCC C, Bourne-Again Shell, GCC Make
* Influenced by: Ada 95, Bourne Shell, SQL, and minorly BASIC, PHP, Python
* Usual File Extensions: .sp, .bush
that the old WWW redirects to.
Among other changes, this port now optionally installs some cmake modules,
which I hope I'm installing into the correct place.
