commit f8afe14bb3e263c77bf2701d01c635c5766dcfa1
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed May 20 18:21:23 2026 +0200

dev-python/larixite: add 2026.1.0

2026.1.0 adds requests as a new direct runtime dep (not present in
2025.5.1's pyproject.toml). All other dep bounds unchanged.

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

dev-python/larixite: switch to DISTUTILS_SINGLE_IMPL

dev-python/{pymatgen,mp-api,emmet-core} are now SINGLE_IMPL; multi-impl
consumer with bare $ on them produces
python_targets_python3_*(-)? that the single-impl children can't expose.
Convert to single-impl too; the SINGLE_IMPL trio on bare
$, multi-impl deps wrapped in python_gen_cond_dep.

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

dev-python/larixite: add upstream pymatgen lower bound

Upstream pyproject.toml lists `pymatgen>=2025.6.14`; the ebuild left
the version unconstrained. Tighten the bound so the dep tree mirrors
upstream's declared minimum.

commit 92cc8000c8e38dbf069b68ca217af0873dcad1e4
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Wed Apr 22 22:31:20 2026 +0200

*/*: normalize personal-maintainer metadata.xml

Unify the three styles that had accumulated across the overlay
(pf-sources-style tab+email-only, bidict-style 2-space+name,
plus a handful of one-off indents) onto a single canonical form:

- DTD URL on https
- 2-space indentation
- <maintainer type="person"> with both <email> and
<name>Ivan S. Titov</name>

Only the Titov maintainer block is touched; co-maintainers and
::gentoo proxy-project maintainers in forked packages are left
as-is. 66 files changed; pkgcheck scan identical before and
after.

commit 2f56c9c36a03d5e556ba4542f3eb31270f64d97f
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Apr 21 17:40:49 2026 +0200

dev-python/larixite: new package, add 2025.5.1

CIF + crystal-structure helpers used by xraylarch. The core reason
we've been threading through pymatgen-core / pymatgen / pymatgen-io-
validation / emmet-core / mp-api / monty / palettable / numdifftools /
sqlalchemy-utils in the preceding commits: xraylarch 2025.3.0+ hard-
imports `from larixite.amcsd import ...` at the `larch.xrd`
package-init level.

RESTRICT=test because upstream's suite reaches out to AMCSD and the
Materials Project API over the network.

Tested: `ebuild ... clean install` is clean.
Signed-off-by: Raukaan Cogbrother <cogbrother@raukaan.local>