commit 516aba7ed83e48e8b7527015c608035d33ecfee9
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jul 28 01:08:03 2026 +0200

sci-physics/mantid: drop 6.15.0.4-r1 and 6.16.0.1-r1

Retention keeps the last two releases plus a rollback target; these are
neither, and no atom anywhere in the tree matches only them.

6.16.0.1 is the more clear-cut removal of the two. Its upstream patch tag was
the one that shipped a deprecation guard set to the Qt6 baseline while
the source still used Qt-5.15-era APIs, which broke the Qt5 build - the
ebuild carried a src_prepare revert for that and nothing else needed it.
The flag has since gone back to a value Qt5 tolerates, so the workaround
retires with the version that required it.

6.16.1-r1 stays deliberately even though the newest release can now
build Qt5 through a USE flag. That path needs a deprecation-guard
rewrite of our own to compile, whereas 6.16.1-r1 builds Qt5 as upstream
shipped it - worth keeping as the unpatched reference while the flag is
new.

The shared webwidgets patch is untouched: all remaining versions apply
it, so nothing is orphaned by this.

commit f0be845b1ec7209748d46344d3910d7c53a16a82
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jul 28 00:16:44 2026 +0200

sci-physics/mantid: select the Qt toolkit by USE flag in the live ebuild

Mirrors the flag layout, the lz4 dependency and the Qt-binding pin from
6.16.1.1 so both ebuilds present the same interface. Upstream main sets
MANTID_QT_VERSION to 6 for every platform now, but still accepts 5 and
still carries the full Qt5 branch, so the choice remains real here.

Two things differ deliberately from the fixed-tag ebuild.

The deprecation-guard workaround is advisory rather than fatal. On a tag
the flag either matches or the ebuild is wrong, so a failed rewrite
should stop the build. Against a moving branch upstream may fix the
spelling, change the value or drop the flag, and none of those warrant a
hard failure - so a missing pattern warns and explains what to re-check
instead.

Verification is proportionate to the target. The fixed tag got a full
compile and install on both toolkits; this one gets configure on both,
since a compile here validates a tree that will have moved by tomorrow.
Both resolve their dependencies and select the requested toolkit, and
the Qt5 rewrite was confirmed applied in the checked-out source rather
than inferred from the absence of a warning.

USE=qt5 is the fragile flag here and the header says so: nothing on
Linux defaults to Qt5 upstream any more, so their CI never compiles this
configuration and a future failure is drift rather than a regression.

commit 1289152d90f4bfa914d23ee7fb5b56581be0db91
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 23:54:02 2026 +0200

sci-physics/mantid: select the Qt toolkit by USE flag

6.16.1.1 is the first release to expose MANTID_QT_VERSION, so both
toolkits become selectable from one ebuild instead of one being frozen
in. qt5 and qt6 are exactly-one-of; qt6 is default because it is what
upstream builds on Linux. Previously the only route to a Qt5 mantid was
keeping an older version in tree purely as a fallback, which costs a
retained version and blocks the qscintilla mask from ever being lifted.

Three defects surfaced while exercising the result, none of which a
clean build or a lint pass reveals:

dev-python/lz4 was never declared but is mandatory on Linux. The
workbench exception handler imports a module whose first statement is a
bare `if is_linux(): import lz4.frame`, so the framework and the Python
bindings both work and only the GUI collapses. Upstream lists it in the
Linux-only branch of its own recipe.

The Qt binding was resolved wrongly. qtpy reads QT_API and falls back to
pyqt5 - it does not prefer the newest binding available - while mantidqt
loads a toolkit-specific extension chosen by that same variable, and
only the one matching the configured toolkit is ever built. Any host
that also carries pyqt5, which every Qt5 mantid pulls in, therefore got
a mismatch. The launcher now pins the binding it was linked against
while still honouring an explicit override.

The Qt5 path does not compile at this tag. Upstream renamed its
deprecation guard from QT_DISABLE_DEPRECATED_UP_TO to
QT_DISABLE_DEPRECATED_BEFORE without changing the value. Qt 5.15 does
not know the former and silently ignores it, but does honour the latter,
where the stated version is inclusive - so every API deprecated in 5.15
vanishes, including one the source still uses behind its own Qt-version
guard. Restoring the earlier spelling for the Qt5 build is enough; the
Qt6 build keeps upstream's flag untouched.

commit 712398b0fbd87be010a4e2f9e80c08b860132284
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 18:27:20 2026 +0200

sci-physics/mantid: move the live ebuild to Qt6

Upstream main now sets MANTID_QT_VERSION to 6 unconditionally: the
per-platform default 6.16.1.1 introduced was removed again by "Move
Windows and macOs to Qt6" (#41896), so HEAD builds Qt5 on no platform.
Leaving the live ebuild on Qt5 atoms would have meant declaring a
toolkit the source no longer selects.

Same dependency mapping as the 6.16.1.1 tag - qtbase:6 plus
qttools:6[assistant] in place of nine Qt5 atoms, pyqt6 for pyqt5, and
qtpy on its pyqt6 flag - and the Windows-only qt.conf sed goes with them.
The cmake value is pinned rather than inherited because upstream has
moved that default twice inside a month.

Configure verified against HEAD; the compile and install phases were
verified on the identical dependency set at the 6.16.1.1 tag rather than
re-run here, which the ebuild comment records.

commit 89809de6071a87e0844a844a1d38ad355b4499ab
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 18:13:06 2026 +0200

sci-physics/mantid: add 6.16.1.1, built against Qt6

6.16.1.1 introduces MANTID_QT_VERSION and defaults it to 6 on Linux, so
carrying the Qt5 packaging forward would have meant configuring against a
toolkit upstream no longer builds by default on this platform. The value
is pinned explicitly rather than inherited, so a later change to that
default cannot silently relink the package.

The Qt5 atoms map onto two: dev-qt/qtbase:6 for Core, Gui, Widgets,
Concurrent, Network, PrintSupport, Xml, OpenGL and Test, and
dev-qt/qttools:6[assistant] for QtHelp. qtsql:5 has no direct successor -
mantid requests no Sql component itself, and the libQt6Sql the build links
comes from qttools[assistant] pulling qtbase[sql,sqlite] for QtHelp.
dev-python/pyqt5 becomes pyqt6 and qtpy switches to its pyqt6 flag; PyQt6
ships no Python resource compiler, so upstream builds the workbench
resources with Qt rcc and no PyQt5 build tool is required.

The qt.conf rewrite the Qt5 ebuilds performed is dropped rather than
retargeted. Its "Prefix = ../lib/qt5" sits inside an if(WIN32) block at
6.16.1 as well as here, so it was never reached on Linux; the Linux
install writes no qt.conf and Qt resolves plugins from the system prefix.

commit 69979589cc1112e1d943e7187400bf64f7939e3a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 09:27:11 2026 +0200

sci-physics/mantid: declare the pydantic dependency

Upstream lists pydantic >=2.11.4,<3 in pixi.toml's plain [dependencies]
table, not in any [feature.*] table, so it is part of the runtime set
rather than a build or docs extra. That table is the one the RDEPEND
here already mirrors -- python, numpy, scipy, matplotlib and h5py all
sit in it -- and pydantic was the entry with no counterpart.

Checked at each tag these ebuilds actually check out, since EGIT_COMMIT
is v$ rather than a branch: v6.15.0.4, v6.16.0.1 and v6.16.1 all
declare it, so all three releases and the live ebuild get it.

Evidence here is upstream's declared dependency table rather than an
observed import: these ebuilds build from a git checkout, and confirming
the call site would have meant cloning the full repository. The
declaration is the same standard applied to the other dependency fixes
in this series.

Range mirrors upstream. gentoo currently carries 2.13.4, which satisfies
it.

commit 0d9e4fdbfaa2eef71bcac26900b3a697fa55bd90
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Jul 5 12:16:51 2026 +0200

sci-physics/mantid: refresh 9999 build-verification note

Re-verified the live ebuild against current HEAD (commit f48e1a58,
derived version 6.16.20260701.1953.dev4): full unpack/prepare/configure/
compile/install pipeline clean on gcc-16 + Boost-1.90 + Qt-5.15.19 +
Python 3.13, install ~253 MiB. Updates the stale gcc-15 / Qt-5.15.18 /
~178 MiB / "as of 6.15.x" wording to match. Records that HEAD carries a
Qt5-safe QT_DISABLE_DEPRECATED_BEFORE=0x050F00 flag (only pre-5.15
deprecations), so no flag-revert sed is needed here, unlike on the
6.16.0.1 patch tag; flagged to re-verify since upstream flip-flops it.
Also syncs the never-taken else-branch EGIT_COMMIT to the v$
form the released ebuilds use.

commit 042721c263b6c55827f45629a4be067566d0bd85
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Jul 5 12:16:51 2026 +0200

sci-physics/mantid: drop 6.15.0.4_rc1, 6.15.0.4_rc3

commit ef4ceb7c2003bbbad9012ea0e59cea73e0a9e724
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Jul 5 12:16:51 2026 +0200

sci-physics/mantid: drop 6.16.0

commit d624f0b2dfd79e912503392a5282b0576ea66734
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Jul 5 12:16:51 2026 +0200

sci-physics/mantid: add 6.16.0.1

This patch tag's top CMakeLists sets QT_DISABLE_DEPRECATED_BEFORE=0x060000
-- a Qt6-readiness switch (upstream is mid Qt5->Qt6 migration) that removes
every Qt5-era deprecated API. mantid's own code still calls some of those
(e.g. the recursive-QMutex ctor in WorkspaceTreeWidget), so the flag breaks
the Qt5 build outright. A src_prepare sed restores the milder
QT_DISABLE_DEPRECATED_UP_TO=0x050F00 form that 6.16.0 and 6.16.1 use,
keeping the package buildable on a Qt5-only Gentoo. Only this tag needs the
sed.

commit 16bcead09b6365db8d87e8eaa540143c4920bfa4
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Jul 5 12:16:51 2026 +0200

sci-physics/mantid: add 6.16.1

commit 2e18434eef57a2e5326a81303948df53ed794c38
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jun 25 19:13:01 2026 +0200

sci-physics/mantid: add 6.16.0

Major bump from the 6.15 line with no build-interface change: upstream
keeps the Qt 5.15 floor, python 3.12, numpy 2.1, hdf5 1.14, eigen 3.4 and
hdf4 4.2, the tree still carries no .cu/.cuh or find_package(CUDA), and
WebEngine stays removed from workbench -- so the ebuild is a pure version
bump off 6.15.0.4.

commit 8833ae3e3dad49b2486c4d488cc4424b061c0d49
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jun 25 19:12:51 2026 +0200

sci-physics/mantid: add 6.15.0.4

Final stable of the 6.15.0.4 line, superseding the _rc3 we shipped; same
code as the rc, so the workbench WebEngine-removal fix carries over.

commit 7cd4c04ef47d39abbba0c1c40491727ce63609f6
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Jun 21 15:39:12 2026 +0200

sci-physics/mantid: correct dependency declarations

A from-clean dependency resolution (and workbench startup) surfaces five
declaration bugs that a local build masks through incidentally-installed
host packages:

* The 23 multi-impl Python deps were tagged [$]. In
a DISTUTILS_SINGLE_IMPL package depending on python-r1 packages that
expands to a placeholder sentinel, making the atoms unparseable and the
package impossible to emerge. Wrap them in python_gen_cond_dep with
[$]; the genuinely single-impl deps (euphonic, pyvista,
pyvistaqt, and the test-only pre-commit) stay on [$].

* sci-libs/hdf (HDF4) is required by the build (CommonSetup.cmake calls
find_package(HDF4 REQUIRED)) but was only named in a comment, never in
RDEPEND. Declare it.

* sci-libs/hdf5 must carry [cxx]: the NexusGeometry framework uses the
HDF5 C++ API (H5Cpp / H5::) across dozens of source files.

* x11-libs/qscintilla must carry [qt5(-)]: mantid is a Qt5 application and
links libqscintilla2_qt5. ::gentoo's qscintilla dropped the qt5 flag, so
the (-) default keeps the overlay's qt5-capable build selectable.

* dev-python/pyqt5 must carry [gui,widgets,printsupport]: the workbench
imports QtGui / QtWidgets / QtPrintSupport through qtpy, and all three
module flags default off, so a clean install otherwise yields a workbench
that cannot start.

commit b198edd9b4db678c8e6699e9e51117818d8e6eb0
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Jun 21 09:58:53 2026 +0200

sci-physics/mantid: add 6.15.0.4_rc3

commit e1579093efda8635fd2004d40dcc08ae7b51e8b3
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun May 10 21:09:12 2026 +0200

sci-physics/mantid: switch to DISTUTILS_SINGLE_IMPL

dev-python/{euphonic,pyvista,pyvistaqt} are now SINGLE_IMPL — mantid's
workbench/Python wrappers do direct imports of these for plotting and
inelastic-neutron-scattering helpers, so the Python-target match needs
to be enforced. Multi-impl mantid with bare $ on them
produces python_targets_python3_*(-)? that the single-impl children
can't expose. Convert both versions; sweep $ →
$ across the RDEPEND (mantid is a cmake+Python
hybrid; uniform PYTHON_SINGLE_USEDEP is simpler than a partial
python_gen_cond_dep wrap and matches single-impl idiom).

commit b3f9b271add758ccbde51bab98a36bc1e8e6697f
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Apr 30 14:02:40 2026 +0200

sci-physics/mantid: bump 6.15.0.3 -> 6.15.0.4rc1

Drops 6.15.0.3 for v6.15.0.4rc1 — the older tag hard-imports
QtWebEngineWidgets at workbench startup, which ::gentoo no longer
satisfies (PyQtWebEngine and dev-qt/qtwebengine:5 are both gone with
the Qt5 deprecation). v6.15.0.4rc1 is the first tagged release with
WebEngine fully removed from workbench/mantidqt.

EGIT_COMMIT now strips Gentoo's prerelease underscore so PV
`6.15.0.4_rc1` resolves to the upstream tag `v6.15.0.4rc1`.

Verified end-to-end: full rebuild + qmerge at MAKEOPTS="-j20",
/opt/mantid 225 MiB, `QT_API=pyqt5 /opt/mantid/bin/workbench` reaches
the Qt event loop with welcome banner.

commit 2da73524f354c1e2905c0579f52fb6422d5f8e00
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Apr 30 13:36:01 2026 +0200

sci-physics/mantid: document QT_API=pyqt5 + invocation in pkg_postinst

The merged install needs three pieces of env state to launch:
* QT_API=pyqt5 (forces qtpy to use PyQt5; default routes to PyQt6
which lacks Qt5-era widgets mantid imports)
* LD_PRELOAD=libtbbmalloc_proxy.so.2 (perf-only TBB allocator)
* PYTHONPATH covering site-packages + bin + plugins (env.d-wired)

Spell out both the full env-prefix form and the post-source-profile
short form, and point at launch_mantidworkbench.standalone as the
recommended wrapper that handles the LD_PRELOAD piece automatically.

commit 07e39f688c5f9109d859fffcfc3039dc00ee170a
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Apr 30 13:29:23 2026 +0200

sci-physics/mantid: use [pyqt5(-)] default on qtpy dep

Quiets pkgcheck MissingUseDepDefault. The semantics are unchanged:
match qtpy with USE=pyqt5 enabled, treat the flag as absent (=fail)
on any qtpy version that doesn't carry it. ::gentoo's qtpy-2.4.3-r2
correctly fails to satisfy; this overlay's qtpy-2.4.3-r99 (USE=pyqt5)
does.

commit 54ff11cc811602ee6e5d6d4d91de1f4681f20857
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Apr 30 13:28:41 2026 +0200

sci-physics/mantid: add pyvista/pyvistaqt/superqt/orsopy to RDEPEND

Mantid 9999's workbench imports pyvista (3D plotting), pyvistaqt
(its Qt glue), superqt (extra widgets) and orsopy (ORSO reflectometry
file format) at runtime. Without them, workbench setup() bombs at
`from instrumentview.FullInstrumentViewWindow import ...`.

Also pin qtpy[pyqt5] so emerge picks the overlay's qtpy-2.4.3-r99
fork (USE=pyqt5) automatically — without that, emerge would resolve
to ::gentoo's qtpy which forces PyQt6 and fails on QDesktopWidget.

The same RDEPEND update is applied to 6.15.0.3 even though that
version is currently un-launchable (Qt5 WebEngine wall) — keeps the
two ebuilds aligned for when upstream ports any further dropped deps
back, and the deps are correct as a static description regardless.

commit ce1b0faafea60dfafd606fd4fc3e09bed1df7621
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Apr 30 12:06:29 2026 +0200

sci-physics/mantid: fix Python wrapper + workbench install

Until now the merged install was unusable: only the C extension
.so files (installed via cmake's TARGETS rules) made it into
/opt/mantid/lib/python3.13/site-packages, while every Python wrapper
(mantid/__init__.py, mantid.simpleapi, the entire workbench/ package,
etc.) silently disappeared. Three issues were stacked:

1. The src_prepare sed only patched the build-time
`pip install --editable .` line in PythonPackageTargetFunctions
.cmake. The same file has a second pip call inside install(CODE
...) that runs at `cmake --install` time and is what actually
places wrappers into the image dir. That call had no --prefix /
--root, so under portage's install phase it tried to write to the
live host's site-packages and PEP 668 silently rejected it.

2. dev-python/vcs-versioning is installed system-wide and auto-hooks
every setuptools build via an entry-point. mantid's pyproject.toml
has no [tool.setuptools_scm] / [tool.vcs-versioning] section, so
the file finder fell back to running git inside the source tree.
Because pip in the install phase runs as root while $ is owned
by the portage build user, git refused with "dubious ownership"
and metadata generation died.

3. Upstream's two launchers (launch_mantidworkbench, .standalone) are
shaped for a conda layout: one checks $CONDA_PREFIX, the other
hardcodes $/bin/python. Both fail under the Gentoo
/opt install.

Fixes:

- Extend the src_prepare sed to also rewrite the install-time pip
command with --break-system-packages --no-build-isolation
--prefix=$ --root=\$ENV. The
literal \$ENV is preserved so cmake evaluates it at
install time, which is when DESTDIR is meaningful.
- Inject SETUPTOOLS_SCM_PRETEND_VERSION and
SETUPTOOLS_SCM_IGNORE_DUBIOUS_OWNER=1 into the cmake -E env
wrapping. The latter is what the vcs-versioning git file finder
explicitly checks; with it set the finder gracefully returns None
instead of raising SystemExit, and setuptools' default file
discovery takes over.
- src_install: drop launch_mantidworkbench (conda-only) and rewrite
launch_mantidworkbench.standalone to use the system Python with a
PYTHONPATH that includes site-packages.
- env.d PYTHONPATH now covers site-packages + bin (Mantid.properties
is bin-relative and resolved via _bin_dirs() walking sys.path) +
plugins (algorithm/qt5 .so loaders).

Verified: full clean rebuild + qmerge of mantid-6.15.0.3 lands
~225 MiB under /opt/mantid, with mantid/mantidqt/workbench/
instrumentview/mantidqtinterfaces all importable. The framework
loads ("Welcome to Mantid 6.15.0.2rc4+uncommitted"), kernel
.version_str() returns the correct version, and workbench.app.main
.main is callable. KEYWORDS still empty: mantid.simpleapi has a
separate Python 3.13 compat bug in funcinspect.lhs_info (CALL
bytecode layout change), unrelated to packaging.

commit e9ba4a5f99fcb635e46e45c7735029434ffcfa5d
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Apr 30 00:52:35 2026 +0200

sci-physics/mantid: bring 9999 to parity with 6.15.0.3 build logic

The 9999 ebuild was effectively a stub — declared deps but missing
the cmake inherit, src_prepare/configure/install overrides, the
/opt/mantid prefix, the no-qt5-webwidgets PATCHES entry, and the
[cxx] USE on sci-libs/nexus. Without those it couldn't even reach
src_configure.

Make 9999 a verbatim copy of 6.15.0.3 — the inline `if [[ $ =
*9999* ]]` already picks EGIT_COMMIT=HEAD vs v$, so the same
file works for both PVs.

Three further changes shared between both ebuilds:

- Rename files/mantid-6.15.0.3-no-qt5-webwidgets.patch ->
files/mantid-no-qt5-webwidgets.patch (drop the PV from the
filename so the same patch can be referenced by both ebuilds via
$ instead of $).
- Replace the static PATCHES array with a conditional eapply in
src_prepare. The patch removes a "Prefer WebEngineWidgets over
WebKitWidgets" block that fatal-errors when neither qtwebengine:5
nor qtwebkit is installed; both are last-rited in ::gentoo.
Upstream main has already deleted the block (mantid-9999 fetches
HEAD which is ~25k lines past v6.15.0.3), so we grep for the
block before applying.
- KEYWORDS comment refreshed to record what 9999 also passes:
unpack/prepare/configure/compile/install all clean against
gcc-15 + Boost-1.90 + Qt-5.15.18 + Python-3.13 (~179 MiB
installed under /opt/mantid). Runtime behaviour still untested.

mantid HEAD is still Qt5-only — 0 find_package(Qt6...) calls,
0 Qt6:: link target references; the Qt5 deprecation pressure from
::gentoo is the same as 6.15.0.3.

commit 5b4d3277667e746178f4236025415a02bb409c4e
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Apr 29 23:54:00 2026 +0200

sci-physics/mantid: full build verified, slot all Qt deps to :5

Successful run of doas ebuild ... clean unpack/prepare/configure/
compile/install on a gcc-15 + Boost-1.90 + Qt-5.15.18 + Python-3.13
host: configure passes after adding dev-qt/qthelp:5 (the previously-
implicit dependency that mantid's qt/widgets/common/CMakeLists.txt
hard-requires for Qt5Help), compile finishes through 3015 ninja
targets without errors, and install lands ~178 MiB cleanly under
/opt/mantid/.

Replace the unslotted dev-qt/qtbase with the explicit Qt5 module
list mantid actually links against (qtconcurrent, qtgui, qthelp,
qtnetwork, qtprintsupport, qtsql, qtwidgets, qtxml — all :5). qtbase
unslotted would have resolved to qtbase:6, which doesn't help us
since the whole codebase is QT_DISABLE_DEPRECATED_UP_TO=0x050F00 and
links _Qt5 suffixed targets throughout.

Pkgcheck now reports DeprecatedDep on the new explicit qt:5 deps
plus the long-standing pyqt5 + versioningit warnings; all four are
the same upstream policy item (Qt5 / pyqt5 / versioningit are
masked-for-removal in ::gentoo). Real fix is upstream Qt6 port,
tracked in earlier memory; no overlay action.

Apply the same Qt5 slot list to mantid-9999 and refresh the
maintainer comment to record what's now verified vs still untested
(runtime behaviour past install).

commit 946b3d5e6f85aa6d17632eb69d8c14152e056548
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Apr 29 23:16:52 2026 +0200

*/*: normalize metadata.xml DTD URL and indent

Repo-wide sweep: 144 metadata.xml files updated to use the
https://www.gentoo.org/dtd/metadata.dtd DTD URL (was http://) and
2-space indentation (was tabs). Maintainer blocks left untouched —
the 2026-04-22 normalization sweep added <name> alongside <email>
where the maintainer was Ivan, but third-party maintainer entries
(lebedev.vasya@gmail.com, megagreener@gmail.com, brothermechanic@gmail.com,
etc.) keep their email-only blocks since we can't safely guess the
corresponding <name>.

pkgcheck stays silent on all metadata-* and maintainer-* checks.

commit 44010bc63e45657d06fa47cfa4c5a63b701f1cf2
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Apr 29 18:30:22 2026 +0200

sci-physics/mantid: refresh maintainer note (HDF4 blocker, no GPU)

Two updates to the comment block under KEYWORDS: * The earlier 'blocked at the HDF4
probe by Gentoo bug 942866' line is stale: this overlay's sci-libs/hdf-4.2.16
builds clean against gcc-15. Confirmed by emerging it on a CUDA 13.2.1 + gcc-15
host; no patch needed beyond what's already in the stuff ebuild. * Add a 'no GPU
offload' note. The brother-machine briefing flagged mantid as 'does GPU compute via
cuda-toolkit when present'. A source-tree audit of v6.15.0.3 finds no .cu/.cuh
files, no find_package(CUDA) / enable_language(CUDA) calls, no nvcc/cuFFT/
cuBLAS/OpenCL/SYCL/HIP/Kokkos references in any CMake; only TBB and OpenMP for CPU
parallelism. So there's no `cuda` IUSE to expose here even with nvidia-cuda-toolkit
installed. KEYWORDS stays empty — mantid still hasn't been verified through a full
build on this host, just unblocked at configure.

commit 53dcdfe41ba0102af49518c636e61d6e1390a87d
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Apr 22 16:59:49 2026 +0200

sci-physics/mantid: install under /opt/mantid instead of /usr

Upstream's CMake install spews data into top-level /usr children
(instrument/, plugins/, scripts/) rather than FHS-compliant
/usr/{lib64,share}/mantid/..., and the project ships as a monolithic
bundle. A single /opt/mantid prefix matches that shape better than
trying to split files across /usr subdirectories via a large patch set.

- CMAKE_INSTALL_PREFIX=/opt/mantid
- Drop the LIB_DIR=lib->lib64 sed (multilib-strict doesn't reach
/opt paths; upstream's default lib/ works inside the /opt prefix).
- Change the qt.conf sed to use an absolute /usr/lib64/qt5 path
rather than a relative ../lib64/qt5, since under /opt the relative
path points at the wrong tree.
- Install /etc/env.d/99mantid wiring PATH, ROOTPATH, LDPATH, and
PYTHONPATH into /opt/mantid/.
- Add pkg_postinst elog explaining the /opt decision and prompting
env-update + shell reload.

Install tree verified: ~180 MiB under /opt/mantid/{bin,include,instrument,
lib,lib64,plugins,scripts}, only README.md lands in /usr/share/doc
(standard cmake.eclass einstalldocs).

commit 5a201bcef8fdb4f297cdd996d8f1536bd536da84
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Apr 22 16:33:53 2026 +0200

sci-physics/mantid: make 6.15.0.3 actually build on current ::gentoo

Build-verified through src_install. The fallout from ::gentoo's Qt5
deprecation schedule plus a few upstream quirks required:

- Local patch mantid-6.15.0.3-no-qt5-webwidgets.patch: mantid's
qt/widgets/common/CMakeLists.txt hard-requires either
Qt5::WebEngineWidgets or Qt5::WebKitWidgets; both are gone from
::gentoo (qtwebengine:5 last-rited 2025-04-28, qtwebkit long
before). The C++ side never calls QWebEngine*; only the Python
help-browser imports QtWebEngineWidgets via qtpy and handles its
absence at runtime. Replace the detect block with empty stubs.

- src_prepare sed for LIB_DIR: upstream hardcodes LIB_DIR=lib in
buildconfig/CMake/LinuxPackageScripts.cmake, which installs shared
libs to /usr/lib on amd64 and trips multilib-strict. Patch to
lib64.

- src_prepare sed for pip flags: PythonPackageTargetFunctions.cmake
invokes `pip install --editable . --ignore-installed --no-deps`
via `cmake -E env`. Two Gentoo-specific flags are needed but the
PIP_* env-var equivalents don't survive portage's ninja/cmake-E-env
wrapping (verified: same env vars work through cmake -E env
*outside* the sandbox). Bake the flags into the command line:
--break-system-packages: defeat PEP 668 refusal (the install
only writes an .egg-link into the build dir, doesn't touch /usr).
--no-build-isolation: use system dev-python/setuptools instead
of pip trying to fetch its own from pypi under network sandbox.

- src_configure mycmakeargs: gate ENABLE_DOCS on USE=doc so the
configure step doesn't fail looking for mantid_sphinx_theme (not
packaged in ::gentoo) when the user didn't ask for docs.

Also add pyqt5/pyqt5-sip to profiles/package.unmask: ::gentoo
last-rited both on 2026-04-21 (removal 2026-05-21); mantid still
hard-requires them.

Still installs to /usr/{instrument,plugins,scripts} (FHS violations);
that's an upstream layout issue, addressable separately.

commit d15f67656cf28bf1e0f48c22678ba35ac8953de8
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Apr 22 13:15:16 2026 +0200

sci-physics/mantid: add 6.15.0.3

Upstream v6.15 rewrote the build system to drop the CMake-side
external-source fetchers for Span, PyStoG, mslice, and googletest.
The 6.12-era src_unpack (which cloned those 4 auxiliary repos into
local paths) plus the matching src_prepare seds that rewrote fetch
URLs are all dead code now:

- Span is vendored directly at Framework/Kernel/inc/MantidKernel/span.hpp
- GoogleTest uses find_package(GTest CONFIG REQUIRED) against the
system dev-cpp/gtest (added to RDEPEND)
- Span.cmake, PyStoG.cmake, scripts/ExternalInterfaces/CMakeLists.txt
are entirely gone from the tree
- Framework/Parallel/src/IO/Chunker.cpp was refactored out, retiring
the gcc:13 stdint.h include hack
- Framework/CMakeLists.txt now includes CMakePackageConfigHelpers on
its own, retiring that sed too

Kept the seds that are still load-bearing:
- FindOpenCascade.cmake path remaps for /usr/{include,lib64}/opencascade
- PreviewManager.h stdexcept include (still missing upstream)
- workbench CMakeLists.txt lib/qt5 -> lib64/qt5

Added a sed to drop 'system' from the Boost required-components list:
dev-libs/boost-1.90 made boost_system header-only and no longer ships
a cmake config for it, so find_package otherwise fails.

Also dropped the EGIT_CLONE_TYPE='single' override (user variable,
and 'single' is already the git-r3 default -- pkgcheck flagged it as
EclassUserVariableUsage).

Build-verify progressed through src_configure past the Python / gtest /
Poco / Boost probes; blocked afterwards on sci-libs/hdf failing to
compile on gcc 15 -- Gentoo bug 942866, ecosystem-level, unrelated
to mantid or this bump. KEYWORDS stays empty with an inline comment
pointing at the bug as a breadcrumb.

commit 2edd0d8b1fc9cdcc8c4011d772c1ab618020b1c2
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Apr 22 13:15:05 2026 +0200

sci-physics/mantid: drop 6.12.0.2

commit b91cd93a12cb39be1b4976cdc1af27ca13ce34e5
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Apr 21 15:16:42 2026 +0200

*/*: bump PYTHON_COMPAT from python3_ to python3_

::gentoo has dropped python3.11 from most of the scientific Python
stack - scipy, pandas, ipython, sphinx, sympy, etc. all target
python3_ now. Overlay ebuilds still claiming python3_11
support therefore fail to resolve their PYTHON_USEDEP=[...,
python_targets_python3_11(-),...] clauses against those upstream
packages, which is the bulk of pkgcheck's NonsolvableDeps noise.

Sweep PYTHON_COMPAT across the overlay accordingly. Files touched
include 193 pure-python3 ebuilds plus 4 sci-libs/pycifrw ebuilds that
retain the python2_7 target. Commented-out COMPAT lines and one
ebuild using a custom $ array are left alone.

pkgcheck dropped from 710 to 475 lines after this change; specifically
NonsolvableDepsIn{Dev,Stable} fell from 391 to 182 combined.

Users on a python3.11 profile lose access to the updated versions in
this overlay, mirroring what ::gentoo already did to the rest of the
scientific stack.

Signed-off-by: Raukaan Cogbrother <cogbrother@raukaan.local>

commit 333a849082e704941d018a7f0b99678eda18904f
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Apr 21 01:07:29 2026 +0200

*/*: bump PYTHON_COMPAT to python3_

Match the ::gentoo convention (main tree dropped 3.9 / 3.10 support
a while ago). Three mechanical substitutions:

- python3_ -> python3_ (189 ebuilds)
- python3_ -> python3_ (llvmlite)
- python2_7 python3_ -> python2_7 python3_ (pycifrw)

Leaves the legacy python2_7-only ebuilds and dev-python/cython
(special PYTHON_TESTED pattern on the 0.29 series) untouched.

commit d29f54b2641e1f1010bf6f27547a9a271cbadb9d
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Apr 19 14:10:41 2026 +0200

sci-physics/mantid: use canonical LICENSE name

commit 8c16b18cc0a75f06aa4c07d74e0306d0050c4fab
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Apr 19 13:49:14 2026 +0200

sci-physics/mantid: add RESTRICT="!test? ( test )"

commit cdc76cfe24624a9ccd5d7516241062cb5dfdada4
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Apr 19 12:44:02 2026 +0200

sci-physics/mantid: drop unused inherits

commit 3cb67ddf94c50f5ac1c3cfebac42be60cc1b475d
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Sun Apr 19 12:33:09 2026 +0200

sci-physics/mantid: wrap long lines

commit f23ece73c4451e2377c17d8b90acb53bee608563
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Jan 15 21:28:34 2026 +0100

*/*: UPD header, Happy New Year

Signed-off-by: Ivan S. Titov <iohann.s.titov@gmail.com>

commit faa1a6bd0ab2591e7f00f30c0e9a6e14a81f56b3
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Dec 11 12:32:55 2025 +0100

Corrected missing blank line after EAPI warning

Signed-off-by: Ivan S. Titov <iohann.s.titov@gmail.com>

commit bd56ad8c4cfa96514317be4d851cb4fcbd6b8802
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Dec 11 10:40:56 2025 +0100

*/*: adjusting python compat to 3.9 to 3.14

Signed-off-by: Ivan S. Titov <iohann.s.titov@gmail.com>

commit 02fee3b133501e13cd97dc4acb029379621c8d56
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Thu Dec 11 01:05:20 2025 +0100

multiple styling corrections to make pkgscan happy

Signed-off-by: Ivan S. Titov <iohann.s.titov@gmail.com>

commit 75d55441dbb2e55a7102e44b643e2e17cdfbc05d
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Fri Oct 17 21:58:20 2025 +0200

finally upd year to 2025 :)

commit 859f8a58dd0e6cf3750b13784667522fbdc2be18
Author: VasilyLebedev <lebedevv@tcd.ie>
Date: Sun Sep 21 19:54:01 2025 +0100

mantid

does not compile

commit aa18e1f8a435e20b3bf6a4404603c5d93eae5681
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 10 12:00:57 2025 +0200

upd pf-sources

commit b451ac3b81ed540a5ce0bbef96d542cd2a2a0dcd
Author: istitov <istitov@github>
Date: Mon Feb 12 10:45:30 2024 +0100

upd copyright to 2024

commit b97ecc81fea274df6cfa7851b81e35dd8c00480c
Author: istitov <istitov@github>
Date: Mon Feb 12 10:44:23 2024 +0100

dev-utils/cmake -> dev-build/cmake

commit e97580dbdd3ac03321a41aff0c27766006ec9dbf
Author: VasilyLebedev <vasily.lebedev@ul.ie>
Date: Wed Nov 29 14:49:38 2023 +0000

Mantid compiles, but not installs

commit 03b95040c1be798060c6b2407b1eb716d52e8d6b
Author: VasilyLebedev <vasily.lebedev@ul.ie>
Date: Mon Nov 27 23:56:08 2023 +0000

Mantid amended

commit 838c9565907d0e0ff66bc02794fcc0425061fda6
Author: VasilyLebedev <vasily.lebedev@ul.ie>
Date: Mon Nov 27 15:19:57 2023 +0000

Draft of mantid added; not compiling yet