I figured that the FreeBSD 14.3 kernel won't mount an ext[234]fs
created with inline_data option, while fuse2fs can do that.
Let's make that default, and since I've been successfully testing
on my amd64 computers with ALLTESTS (without SLOWTESTS), switch.
from e2fsprogs to util-linux, to complete the bump of all users
of either library that started with Alexander's commit titled
'*/*: Switch to misc/libuuid and misc/libblkid'
PR: 251489
in libuuid, also replace mkdir --parents GNUism by POSIX mkdir -p
to avoid MANPAGES build issue.
While here, clean up with portfmt/portclippy.
PR: 251489
The r_corrupt_fs self-test seems to have failed often recently on
various builders with a timeout, which I cannot reproduce. Disable
unless SLOWTESTS is set, and extend timeout from 3 to 10 minutes.
Not bumping PORTREVISION because this does not change the package
contents, only helps a "have package" or "failed build" situation.
EXT_SUFFIX, according to PEP 3149, refers to the full tag and
extension for compiled extension module objects, eg .cpython-311.so,
.cpython-313t.so, etc. We do not use the correct semantic meaning,
and this usage becomes ambiguous and confusing when tags do not
match between bytecode and compiled extension module objects.
Rename our PYTHON_EXT_SUFFIX to PYTHON_TAG to align with PEP 3147's
specification of a magic tag, which consists of implementation name
and shorthand version only. This is meant for bytecode and other
files containing this tag in their filename that do not depend on
a specific Python ABI for the same version. Chase all existing
consumers.
Introduce PYTHON_SOABI to align with PEP 3149's specification of a
tag, which consists of implementation name, shorthand version and
any ABI flags present (this and PYTHON_TAG are identical without
ABI flags). This is meant for compiled extension module objects and
other files that depend on a specific Python ABI for the same
version.
Add documentation for these variables that our PYTHON_EXT_SUFFIX
never had.
PR: 274671
Event: Kitchener-Waterloo Hackathon 202506
Tahoe-LAFS (Tahoe Least-Authority File Store) is the first free
software / open-source storage technology that distributes your
data across multiple servers. Even if some servers fail or are taken
over by an attacker, the entire file store continues to function
correctly, preserving your privacy and security.
PR: 287130
Approved by: acm (mentor)
Kerchunk is a library that provides a unified way to represent a variety of
chunked, compressed data formats (e.g. NetCDF, HDF5, GRIB), allowing efficient
access to the data from traditional file systems or cloud object storage. It
also provides a flexible way to create virtual datasets from multiple files. It
does this by extracting the byte ranges, compression information and other
information about the data and storing this metadata in a new, separate object.
This means that you can create a virtual aggregate dataset over potentially many
source files, for efficient, parallel and cloud-friendly in-situ access without
having to copy or translate the originals. It is a gateway to in-the-cloud
massive data processing while the data providers still insist on using legacy
formats for archival storage.
We provide the following things:
- completely serverless architecture
- metadata consolidation, so you can understand a many-file dataset (metadata
plus physical storage) in a single read
- read from all of the storage backends supported by fsspec, including object
storage (s3, gcs, abfs, alibaba), http, cloud user storage (dropbox, gdrive)
and network protocols (ftp, ssh, hdfs, smb...)
- loading of various file types (currently netcdf4/HDF, grib2, tiff, fits,
zarr), potentially heterogeneous within a single dataset, without a need to go
via the specific driver (e.g., no need for h5py)
- asynchronous concurrent fetch of many data chunks in one go, amortizing the
cost of latency
- parallel access with a library like zarr without any locks
- logical datasets viewing many (>~millions) data files, and direct
access/subselection to them via coordinate indexing across an arbitrary number
of dimensions
Earlier I bumped the default Go to 1.24. Ports that specify a lower
version will still build with those lower version (for now), so they
don't need a bumping. Instead I'm bumping anything that (now) has go124
as a dependency.
befuse - Be File System (BeFS) FUSE module for userspace
A module that provides a userspace implementation of the BeFS.
Key Features:
- Mount BeFS partitions on FreeBSD.
- Supports reading and writing to BeFS-formatted partitions.
- Compatible with x86_64 systems.
- Easy installation and use via FUSE.
Dependencies:
- FUSE (Filesystem in Userspace) library.
- BeFS-formatted partition or disk image.
WWW: https://github.com/kuku929/befuse
PR: 285352
