On 6/7/25 18:53, Pete Wright wrote:
On 6/7/25 8:44 AM, Guido Falsi wrote:
On 6/7/25 17:18, Pete Wright wrote:
for low power vm's or systems its super wasteful to force
installation of so many small files. rust/cargo is slow enough, but
having to wait ages for rust itself just makes things needlessly more
painful.
IMHO this is better solved by building on more powerful machines and
deploying to low power VMs. CI systems are specific for this kind of
need AFAIK.
But not knowing your specific use case I cannot be sure.
that's my specific use case - automated ci/cd infrastructure that
charges per-min. the main annoyance for developers is that rust is an
ancillary dependency for building python packages and dependencies. for
modules with c it's a non issue because we can generally use the useland
clang/llvm. but having to wait like 60seconds to install 40k+ files
just so rustc can run is a pretty big annoyance - esp when linux based
workflows have already optimized on this front.
the alternative is maintaining our own images for CI/CD...which is a lot
of uneeded admin overhead imho. we already have to jump through enough
hoops to get wheel dists built internally that contain rust code
precompiled as is since the rust community doesn't treat freebsd as a
tier-1 platform. so this is just more friction with little upside for
most use-cases.
This is a very specific thing. Anyway I think the way to get a
"rust-lite" package is via subpackages.
What the best way is to manage your CI environment is a completely
different thing.
--
Guido Falsi <m...@madpilot.net>
