After the 91fdbed776 commit fixing the
issue for MySQL80 introduced another problem for the ports that depends
on php8[01]-openssl port couldn't be built as the fix prevented
php8[01]-openssl from being installed as it's already built with
default php installation. As the problem has grown much bigger now and
php80 is currently the DEFAULT php version so we are switching the
behavior of php8[01] ports making the openssl module as default.
- Remove non-default OPTION MYSQL80 from lang/php8[01]
- Remove ports security/php8[01]-openssl
- Remove OPTION OPENSSL from lang/php8[01]-extensions
- Mark lang/php8[01] to IGNORE with libressl and libressl-devel
Although php builds fine with those most of the extensions do not
as they have dependency on curl. So mark it early.
- OPTIONIZE lang/php80
- Change openssl_DEPENDS to conditional for php74 only as this module
is default from php80 with this commit. php74 do not have the issue
where it fails to connect to MySQL80 due to new caching_sha2_password
- Remove hash_DEPENDS from php.mk as it is a default module for all php
- Change json_DEPENDS to conditional for php74 only as this module is
default from php80
PR: 261797 259793 252420
Reported by: sean@rogue-research.commartin@waschbuesch.de
Approved by: tz (private email) ale (private email)
Sponsored by: Bounce Experts
Asterisk build system checks for presence of xmlstarlet as "xml"
binary on the system.
If found it triggers part of the build system trying to download
some external files during the install phase which even uses a
command line tool not available on FreeBSD.
Such code is not necessary for the port, as all supported modules
are downloaded using ports tree provided functionality. Furthermore
downloading files from the internet is forbidden during the install
phase.
This patch forces the variable used by the Makefiles to identify
xmlstarlet presence to be empty. so the code path described above
is not triggered.
PR: 261884
Asterisk build system checks for presence of xmlstarlet as "xml"
binary on the system.
If found it triggers part of the build system trying to download
some external files during the install phase which even uses a
command line tool not available on FreeBSD.
Such code is not necessary for the port, as all supported modules
are downloaded using ports tree provided functionality. Furthermore
downloading files from the internet is forbidden during the install
phase.
This patch forces the variable used by the Makefiles to identify
xmlstarlet presence to be empty. so the code path described above
is not triggered.
PR: 261884
[1.0.14] 2022-02-10
- include the PMT and teletext PIDs next to the video PID in the Mplayer
output (Robert Bartel <r.bartel@gmx.net>)
- is_nearly_same_frequency() fix
Reported by: portscout
* Fold the TOML option because its dependency is no longer an optional
requirement as noted in "setup.{py,cfg}". This should also fix some
cases with build errors where the TOML option was disabled. [1]
Changelog since 6.3.2:
https://github.com/pypa/setuptools_scm/blob/v6.4.2/CHANGELOG.rst
PR: 259797 [1], 261698 [1]
MFH: No (feature release)
A C/C++ based package for advanced data transformation and statistical
computing in R that is extremely fast, flexible and parsimonious
to code with, class-agnostic and programmer friendly. It is well
integrated with base R, 'dplyr' / (grouped) 'tibble', 'data.table',
'plm' (panel-series and data frames), 'sf' data frames, and
non-destructively handles other matrix or data frame based classes
(such as 'ts', 'xts' / 'zoo', 'timeSeries', 'tsibble', 'tibbletime'
etc.)
WWW: https://cran.r-project.org/web/packages/collapse/
Changes since 52:
DIN Is Noise 53:
/* new in DIN53:
launched drones launch drones that launch drones that launch drones....!
use Drone Params > Defaults > Generations to set the number of times this can happen
if Generations = 1, A drone launcher launches drones (@ a Drones Per Minute)
that die at the end of their lifetimes. This is default and the only behaviour until DIN 52.
if Generations = 2, A drone launcher launches drones that launch drones.
if Generations = 3, A drone launcher launches drones that launch drones that
launch drones too.
if Generations = 4, 5, 6, ... this quickly escalates into a population explosion of drones;
lots of drones birthing lots of drones, living their life out and waiting to die can get
very loud (especially if the Compressor isnt ON), slow down DIN and maybe even your computer
beyond rescue. Be careful! :)
Ways to prevent this population explosion are: keep Generatons low (Menu > Drone Params
> Defaults), keep Drones Per Minute (DPM) and Lifetime on the original
launcher low (Select drone launcher and adjust values from Menu > Drone Params > Motion) and
keep the Fall time low (the fade-out time for drone after being killed, from Menu > Drone
Params > Defaults)
The launched drones take the DPM and Lifetime of their parent so editing carefully the
parameters of the original launcher is important.
/* new default Drones Per Minute (DPM) on a drone launcher (Menu > Drone Params > Defaults). Assigns a
DPM when making a drone launcher. Turn on ~ to assign a DPM at random.
* re: Auto rotation of drone velocity/acceleration vectors:
changed Degrees Per Second to Degrees Per Tick
/* re: Menu > Drone Params > Defaults > Bounces
when set to 0, launched drones dont bounce off the bottom of the microtonal keyboard
but are killed immediately (behaviour until DIN 52)
when set to -1, drones dont bounce off the bottom of the microtonal keyboard at all:
but they are not killed either, they just live their life(time) out
/* gravity base and tip dont move ie stay fixed as you scroll the microtonal keyboard in DIN53.
this is because gravity is now in 'object space' along with the drones and microtonal ranges.
until DIN52, gravity was in 'UI space' along with UI controls.
* repositioned drone arrow UI elements
! fixed : DIN not quitting when frozen drones present !
! fixed : change size of gravity vector when its modulating !
