Add flavor cdda to allow playing and ripping CDs.
The Aqualung port was compiled with cdda until version 2.0. The constant
scanning for a new CD might interfear with other uses of the CD drive.
This new flavor gives the option to users to continue playing CDs with
Aqualung.
OK jeremy@
Add PKGSPEC to the different love/* versions as they don't provide
backwards compatibility. This allows games/indierunner to install the
different versions simultaneously as dependencies.
ok op@ (maintainer)
Make post-extract regex more specific /^v[0-9]/ instead of just /^v/.
This avoids issues project IDs starting with 'v' that use the targetdir
of DIST_TUPLE.
Checked for no change in output with dist-tuple.test. No breakage in a
bulk build.
Introduce a rib entry queue used to split the processing of UPDATES into
two steps.
One of the biggest latency inducing bottlenecks in bgpd is that UPDATE
messages are processed to completion. Updating the Adj-Rib-Out is a
loop over all peers and is therefor super heavy. By taking this part
of the pipeline into its own step we can drop the latency inside the
main poll loop by a lot.
Introduce a per-peer update queue that enqueues the rib entries after
the decision process and then handles those one by one. This also has
a benefit that a single peer can not monopolize the processing in bgpd.
So a single flapping peer should result in far less noticeable delays
on all other UPDATES from other peers.
For now disable the "addpath send all" optimisation since for that
an extra queue of updates needs to be kept. Instead just use the regular
addpath codepath that is less optimised but produces the same results.
With and OK tb@
Build ruby40 FLAVOR for ruby gem ext ports
Skip unicorn, kgio, and raindrops as raindrops test depends on unicorn,
unicorn run depends on kgio, and kgio segfaults at runtime. raindrops
isn't used by a port other than unicorn.
Skip hiera-eyaml and hiera-eyaml-gpg, as hiera-eyaml has a pessimistic
versioning constraint not allowing Ruby 4+, and hiera-eyaml-gpg depends
on hiera-eyaml. This is likely easily fixable just by removing the
pessimistic versioning constraint on Ruby, but since I believe these
are only used by Puppet, there's no real need to support the ruby40
FLAVOR for them until Puppet switches to Ruby 4.0.
