Import minizip-ng and zlib-ng
Minizip was originally developed in 1998. It was first included in the zlib
distribution as an additional code contribution starting in zlib 1.1.2. Since
that time, it has been continually improved upon and contributed to by many
people.
+ Creating and extracting zip archives.
+ Adding and removing entries from zip archives.
+ Read and write raw zip entry data.
+ Reading and writing zip archives from memory.
+ Zlib, BZIP2, LZMA, and ZSTD compression methods.
+ Password protection through Traditional PKWARE and WinZIP AES encryption.
+ Buffered streaming for improved I/O performance.
some ports bundle it, some ports allow building against a systemwide
one, some ports bundle/rely on an incompatible version - all those will be
fixed in following commits.
Mk/Uses: Introduce USES=minizip[:ng]
To simplify, the LIB_DEPENDS part a new USES tag is added.
USES=minizip will add a LIB_DEPENDS on legacy minizip and
USES=minizip:ng will add a LIB_DEPENDS on minizip-ng.
minizip [1]:
databases/spatialite
databases/spatialite-tools
devel/collada-dom
games/mrboom
games/oolite
graphics/comical
misc/xiphos
science/libkml
textproc/sigil
www/domoticz
deskutils/anydesk
emulators/mupen64plus-core
multimedia/assimp
multimedia/vlc
net-im/psi
net-im/telegram-desktop
minizip-ng:
devel/axmldec
[1] Some are known to work with minizip-ng but have to be patched.
Approved by: tcberner (portmgr)
Differential Revision: https://reviews.freebsd.org/D33771
Now that the build system no longer requires python27, this port can be
revived. The port has been completely redone from scratch based on the
current upstream version.
PR: 261402
yuzu package provided "yuzu-cmd" executable but it's very buggy and
hard to use. yuzu-qt5 package provided stable "yuzu" executable.
The split was inspired by citra{,-qt5} but in yuzu confused new users.
The fifth milestone of the soon to be released Wine 7.0 with
30 bug fixes.
Also do not extract the wine-staging files twice, symlink them
instead. [1]
PR: 260612 [1]
Submitted by: Ivan Rozhuk <rozhuk.im@gmail.com> [1]
Approved by: maintainer (= author)
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)
The 4th milestone of the soon to be released Wine 7.0 with 38 bug
fixes, and another 22 bug fixes from the (skipped) RC3 release.
In addition to the patch provided by Damjan, part of the PLIST change
in PR 260612 has been applied to install some files that used to be
dependent on the STAGING option.
Update to the latest pst 6.2 qemu development version for bsd-user.
This removes mips support and includes new system calls like swapoff
with two args. It's also the result of continuing efforts to upstream
changes. It's a devel version, and more dicy than most devel versions,
so caution is advised: it builds but there may be important cases that
are broken.
Sponsored by: Netflix
The swapoff(2) syscall recently changed from taking a single
argument to taking two (adding a field used for a "force" flag);
this broke qemu-user, since it translates system calls from
guest to host architecture.
Thanks to: imp
With hat: re@
Sponsored by: https://www.patreon.com/cperciva
