commit 3a6ee14b80b6a08b986790ead970937189c2a9ac
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Mon May 5 23:15:16 2025 -0700

tgbugs-meta/sparcron-meta: use BDEPEND for live deps

this makes it possible to use --onlydeps --onlydeps-with-rdeps=n
to build on the live dependencies with ACCEPT_KEYWORDS='**' and not pull
in all the transitive runtime deps, there may still be some issues, but
in that case i think the pattern is to emerge onlydeps the -1 ebuild

commit 747d6bfd11753c5e5d626dd9b62aac8c3119e306
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Mon May 5 22:57:55 2025 -0700

tgbugs-meta/sparcron-meta: add live meta

commit 9cb8a14ca3e77375aff1e5bfef917dfa85fad3b2
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Tue Apr 22 17:19:42 2025 -0700

tgbugs-meta: drop x86 and arm, add HOMEPAGE

commit 16984e347df06a812ae3d4da887efbab58b97b01
Author: Tom Gillespie <tgbugs@gmail.com>
Date: Tue Apr 22 00:21:13 2025 -0700

tgbugs-meta: added category for meta packages

I considered a bunch of different names for this category,
but as soon as I started naming the individual ebuilds I
realized that every single one needed to be prefixed with
tgbugs- to avoid potential collisions with other user meta
packages, yes this means that the number of cateogires for
user meta packages wind up proliferating, maybe the package
manager spec could be updated to mitigate the proliferation
but for now it seems like the best solution.

these come from the various world- specifications in
https://github.com/tgbugs/dockerfiles/blob/master/source.org
and represent various environments that we want to be able to
reproduce and more importantly continually test for issues

don't miss the stupid hack of referring to sed at its full path
to use it at the top level to strip comments out of RDEPEND so
that comments can live inline in the RDEPEND section without
causing portage to get angry, this allows ebuilds to contain
additional documentation about deps in line for anyone trying
to use them as a reference