Inspired by expect(1) but with its own syntax, orch allows program
orchestration via a pts(4) pseudo-terminal driven by similar write/match
patterns as with it source of inspiration.
This is still in relatively early development, but already it has a fair
amount of useful features. Feedback is welcome, examples can be found
both in the manpage as well as /usr/local/share/orch/examples. Other
practical examples can be found at:
https://git.kevans.dev/kevans/tty-tests
- switch to fork [1]
- flavorize to be used against Qt6
- rename port to match upstream (and get rid of the qt-version in the name)
[1] https://gitlab.com/nicolasfella/signond/
AppJail Reproduce is a small open source BSD-3 licensed tool for
automating the creation of images using Makejails, scripts and
simple text files, providing a common workflow and simplifying many
things.
PR: 275500
Approved by: tcberner (mentor)
Differential Revision: https://reviews.freebsd.org/D43151
Autorestic is a wrapper around the amazing restic. While being amazing
the restic cli can be a bit overwhelming and difficult to manage if you
have many different locations that you want to backup to multiple
locations. This utility is aimed at making this easier.
WWW: https://github.com/cupcakearmy/autorestic
PR: 275548
Approved by: submitter is maintainer
KDE's 6th Megarelease - Beta 1
Wednesday, 29 November 2023
En route to the new Plasma, Frameworks and Gear
Every few years we port the key components of our software to a new
version of Qt, taking the opportunity to remove cruft and leverage the
updated features the most recent version of Qt has to offer us.
It has been nearly 10 years since the last big release of our flagship
Plasma desktop environment, and the time has come again. KDE is making
available today the Beta version of all the software we will include in
a megarelease scheduled for the end of February 2024.
To ensure all parts of KDE's software stack are working together, we are
releasing all our major bundles at the same time. Today sees the
continuation of that journey with the Beta releases of Plasma 6, KDE
Frameworks 6 and the KDE Gear bundle of apps.
+-------------------------------------------------------------------------+
| This is a very early preview intended for developers and testers only. |
| We hope it will be picked up by rolling unstable distros, but it is far |
| from being ready for day-to-day use yet. |
+-------------------------------------------------------------------------+
Announcement: https://kde.org/announcements/megarelease/6/beta1/
Obtained from: https://github.com/tcberner/kde6-overlay/
Further port changes:
* graphics/libkexiv2-devel has been added
KDE's 6th Megarelease - Alpha
Wednesday, 8 November 2023
En route to the new Plasma, Frameworks and Gear
Every few years we port the key components of our software to a new
version of Qt, taking the opportunity to remove cruft and leverage the
updated features the most recent version of Qt has to offer us.
It has been nearly 10 years since the last big release of our flagship
Plasma desktop environment, and the time has come again. KDE is making
available today the Alpha version of all the software we will include in
a megarelease scheduled for the end of February 2024.
Announcement: https://kde.org/announcements/megarelease/6/alpha/
Obtained from: https://github.com/tcberner/kde6-overlay/
Further ports specific changes:
* multimedia/phonon: is now flavored for Qt5 and Qt6
xNVMe provides the means to program and interact with NMe devices from user
space. The foundation of xNVMe is libxnvme, a user space library for working
with NVMe devices. It provides a C API for memory management, that is, for
allocating physical / DMA transferable memory when needed. xNVMe is an NVMe
command interface allowing you to submit and complete NVMe commands in a
synchronous as well as an asynchronous manner.
WWW: https://xnvme.io/
Signed-off-by: Karl Bonde Torp <k.torp@samsung.com>
PR: 262032
OpenTofu is an OSS tool for building, changing, and versioning
infrastructure safely and efficiently. OpenTofu can manage existing and
popular service providers as well as custom in-house solutions.
The key features of OpenTofu are:
- Infrastructure as Code: Infrastructure is described using a high-level
configuration syntax. This allows a blueprint of your datacenter to be
versioned and treated as you would any other code. Additionally,
infrastructure can be shared and re-used.
- Execution Plans: OpenTofu has a "planning" step where it generates an
execution plan. The execution plan shows what OpenTofu will do when
you call apply. This lets you avoid any surprises when OpenTofu
manipulates infrastructure.
- Resource Graph: OpenTofu builds a graph of all your resources, and
parallelizes the creation and modification of any non-dependent
resources. Because of this, OpenTofu builds infrastructure as
efficiently as possible, and operators get insight into dependencies
in their infrastructure.
- Change Automation: Complex changesets can be applied to your
infrastructure with minimal human interaction. With the previously
mentioned execution plan and resource graph, you know exactly what
OpenTofu will change and in what order, avoiding many possible human
errors.
WWW: https://opentofu.org
Command::Runner is a perl module that helps
running external commands and Perl code refs,
featuring timeout, quoting and flexible logging.
WWW: https://metacpan.org/dist/Command-Runner
PR: 274779
- Merge all fpc-* units to lang/fpc. It gives us a better way to maintain fpc
and lazarus ports.
- Update Mk/fpc.mk for reflects new changes
- Update Mk/lazarus.mk for reflects new changes
- Now we can defined WANT_FPC_DEVEL AND WANT_LAZARUS_DEVEL for use devel version
of fpc or lazarus for build apps based on fpc/lazarus
- Add entries to MOVED
- Bump PORTREVISON of affected ports
- Some other minor modifications
tailspin works by reading through a log file line by line, running a
series of regexes against each line. The regexes recognize patterns
like dates, numbers, severity keywords and more.
tailspin does not make any assumptions on the format or position of
the items it wants to highlight. For this reason, it requires no
configuration or setup and will work predictably regardless of the
format the log file is in.
WWW: https://github.com/bensadeh/tailspin
This is a port of https://github.com/zxombie/u-boot/tree/bhyvearm64 to
the version of u-boot in the ports tree. There is a bhyve arm64 port
that is close to landing, so now seems like a good time to make the port
available.
In the longer term we would upstream this platform in some form, but
since arm64 bhyve is experimental, I think trying to upstream at this
point is premature. Of course, we prefer not to carry patches in the
ports tree when possible, but in this case it seems justified to do so
for some time, to give users a change to test and report problems.
Approved by: manu
Sponsored by: Innovate UK
Sponsored by: Klara, Inc. (hardware)
Differential Revision: https://reviews.freebsd.org/D42437
eza is a modern, maintained replacement for the venerable
file-listing command-line program ls that ships with Unix
and Linux operating systems, giving it more features and
better defaults. It uses colours to distinguish file types
and metadata. It knows about symlinks, extended attributes,
and Git. And it's small, fast, and just one single binary.
By deliberately making some decisions differently, eza
attempts to be a more featureful, more user-friendly
version of ls.
PR: 273849
LTS support is documented at:
https://cfengine.com/supported-versions/
The sysutils/cfengine-lts and sysutils/cfengine-masterfiles-lts
will track cfengine's LTS branch simliarly to devel/subversion-lts
and devel/jenkins-lts tracking their respective upstream LTS
branches. This port must only be updated in accordance to documentation
at https://cfengine.com/supported-versions/.
PR: 274453
MFH: 2023Q4
Runas is a tool for running commands as another user. It is an
alternative to "sudo", which has a history of serious security issues,
and "su", which is inconvenient for anything but running a shell.
The runas command is a simple wrapper around "su" to streamline its
use. It differs from "sudo" in that it requires the password of the
target user rather than the calling user, and it requires no SUID
permissions or configuration.
