app-office/beancount
A double-entry accounting system that uses text files as input
Screenshots
View
Download
BrowseChangeLog
commit ca8261c4ffaadde41193177e0267b04df6593353
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Aug 3 14:49:49 2026 +0200
*/*: normalize metadata.xml whitespace
Use the overlay-wide two-space XML indentation convention and remove the remaining trailing whitespace so metadata stays consistent and diff-safe.
commit d26e488d095396a8343a1053601f18f59982a8df
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 10:04:12 2026 +0200
*/*: drop dead Python targets from PYTHON_COMPAT
139 ebuilds across 65 packages still listed python3_10, python3_11 or
python3_13t. None of the three is a supported implementation any more:
gentoo's python-utils-r1 sets _PYTHON_ALL_IMPLS to python3_ plus
python3_t, and everything older falls into the branch commented
"implementations deprecated prior to EAPI 9 are fatal".
Inert today, which is why nothing caught it. Targets outside
_PYTHON_ALL_IMPLS are silently dropped rather than rejected, so they
never became USE flags and never produced a dependency atom -- an ebuild
declaring python3_ was only ever offering 12, 13 and 14.
Two reasons to clean them up anyway. The eclass branch they land in
dies for any EAPI other than 7 or 8, so all 139 are waiting to break on
the first EAPI 9 bump. And pkgcheck's OldPythonCompat is a git-scoped
check that only inspects ebuilds touched in a commit range, so it never
reports these on a full-tree scan and would instead fire on whichever
unrelated commit next touches one of them.
No revbump, because nothing observable changes. Verified on a sample
spanning every transformation shape that the python USE flags portage
offers are byte-identical before and after, and that a pkgcheck run
over all 65 packages returns a set-identical list of findings.
The eight python2_7 ebuilds are deliberately untouched: that target is
also absent from _PYTHON_ALL_IMPLS, but they reach it through the
_PYTHON_ALLOW_PY27 hatch in the overlay's forked python-utils-r1_py2.
commit f063ae7ccf95da1ca9cab443c7d716238527e837
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 16 16:02:17 2026 +0200
app-office/beancount: Keyword 3.2.3 for ~arm64
meson C parser (bison/flex-generated); aarch64-portable, no arch-specific code. Unblocks beangulp on arm64.
commit 94304d0f1a1b09453a54b8d89a913317a17ee8f1
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 2 19:17:14 2026 +0200
app-office/beancount: new package, add 3.2.3
meson-python build: meson drives the bison/flex parser generation. Runtime
deps are just click/python-dateutil/regex (import and query tooling live in
beangulp/beanquery). python_test runs --pyargs from $ because the C
extension lands in the meson install tree, not under $.
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Aug 3 14:49:49 2026 +0200
*/*: normalize metadata.xml whitespace
Use the overlay-wide two-space XML indentation convention and remove the remaining trailing whitespace so metadata stays consistent and diff-safe.
commit d26e488d095396a8343a1053601f18f59982a8df
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Mon Jul 27 10:04:12 2026 +0200
*/*: drop dead Python targets from PYTHON_COMPAT
139 ebuilds across 65 packages still listed python3_10, python3_11 or
python3_13t. None of the three is a supported implementation any more:
gentoo's python-utils-r1 sets _PYTHON_ALL_IMPLS to python3_ plus
python3_t, and everything older falls into the branch commented
"implementations deprecated prior to EAPI 9 are fatal".
Inert today, which is why nothing caught it. Targets outside
_PYTHON_ALL_IMPLS are silently dropped rather than rejected, so they
never became USE flags and never produced a dependency atom -- an ebuild
declaring python3_ was only ever offering 12, 13 and 14.
Two reasons to clean them up anyway. The eclass branch they land in
dies for any EAPI other than 7 or 8, so all 139 are waiting to break on
the first EAPI 9 bump. And pkgcheck's OldPythonCompat is a git-scoped
check that only inspects ebuilds touched in a commit range, so it never
reports these on a full-tree scan and would instead fire on whichever
unrelated commit next touches one of them.
No revbump, because nothing observable changes. Verified on a sample
spanning every transformation shape that the python USE flags portage
offers are byte-identical before and after, and that a pkgcheck run
over all 65 packages returns a set-identical list of findings.
The eight python2_7 ebuilds are deliberately untouched: that target is
also absent from _PYTHON_ALL_IMPLS, but they reach it through the
_PYTHON_ALLOW_PY27 hatch in the overlay's forked python-utils-r1_py2.
commit f063ae7ccf95da1ca9cab443c7d716238527e837
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 16 16:02:17 2026 +0200
app-office/beancount: Keyword 3.2.3 for ~arm64
meson C parser (bison/flex-generated); aarch64-portable, no arch-specific code. Unblocks beangulp on arm64.
commit 94304d0f1a1b09453a54b8d89a913317a17ee8f1
Author: Ivan S. Titov <iohann.s.titov@gmail.com>
Date: Tue Jun 2 19:17:14 2026 +0200
app-office/beancount: new package, add 3.2.3
meson-python build: meson drives the bison/flex parser generation. Runtime
deps are just click/python-dateutil/regex (import and query tooling live in
beangulp/beanquery). python_test runs --pyargs from $ because the C
extension lands in the meson install tree, not under $.