mos6510/cycle_based/mos6510c.h:114:7: error: virtual table of type 'struct MOS6510' violates one definition rule [-Werror=odr]
Signed-off-by: Sam James <sam@gentoo.org>
One of ruff's dependency crates is tikv-jemalloc-sys. This supports
linking to the system jemalloc; use it. Compiles a bit faster, produces
somewhat smaller binaries..
* SIZE: 37.74MiB -> 32.37MiB, 29 -> 29 files
* ------> SIZE(-14.21%)
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
It is neither necessary nor desirable to compile and install every
conceivable crate in the ruff source code.
- ruff_dev is "an internal CLI for developers of Ruff"
- ruff_python_formatter is just the source code for `ruff format`, but
compiled standalone with a barebones main.rs for faster dev iteration
- libruff_wasm.so exists solely to implement https://play.ruff.rs which
would matter if we were packaging www-apps/ruff, or if we were using
`--target web`, neither of which is true
- libruff_macros.so is an internal proc-macro and it makes no sense that
it should build a .so to begin with...
We only care about two things:
- ruff, the cli program
- ruff_shrinking, which is a debug tool for producing minimal testcases
of an issue. It is theoretically useful, so can't hurt to distribute.
* FILES:-usr/bin/ruff_dev
* FILES:-usr/bin/ruff_python_formatter
* FILES:-usr/lib64/libruff_macros.so
* FILES:-usr/lib64/libruff_wasm.so
* SONAME:-libruff_macros.so(64)
* SONAME:-libruff_wasm.so(64)
* SIZE: 77.00MiB -> 37.74MiB, 33 -> 29 files
* ------> FILES(-4) SONAME(-2) SIZE(-50.99%)
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
The python module has no functionality. It can be used solely as:
```
python3.11 -m ruff
```
in which case it will check for sys.prefix + '/bin/ruff' and try to run
it.
The downside of trying to install it as a python project is that it:
- adds fuzzy USE flags on python version
- recompiles everything once per python impl, despite attempts at
copying sources around
- adds extra dependencies on e.g. maturin
- generally complicates the ebuild
We don't need any of that since this is just a cargo program.
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
dev-util/buildbot has a new dependency in 3.11 which is missing this
keyword. So dropping keywords here makes sense, and same with other
packages that depend on buildbot (master).
But not all buildbot* packages depend on buildbot (master), so there
wasn't really any reason to drop keywords there...
In particular, the worker has no particular reason to be excluded from
running on riscv and connecting to a master on amd64.
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/35699
Signed-off-by: Sam James <sam@gentoo.org>
Drop old. This is the remaining holdout for dev-python/future.
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
Remove old. Allows cleaning up old buildbot-worker versions too.
Signed-off-by: Eli Schwartz <eschwartz93@gmail.com>
Signed-off-by: Sam James <sam@gentoo.org>
Arthur Zamarin
Sam James
Joonas Niilola
Eli Schwartz