New comment by jcgruenhage on void-packages repository

https://github.com/void-linux/void-packages/pull/24547#issuecomment-686556041

Comment:
> CI doesn't run package checks, so it's possible that one of the many moving pieces involved broke a new release. And even if it did run, checks can't cover all runtime related stuff. At least launching it quickly and being sure that basic functionality is still there is very important.

Luckily that's quite rare with rust (which is the reason I didn't do that stuff for version bumps so far, because I thought the risk was low enough), but I agree. Will compile locally and launch it at least once.

> This isn't a critical package, so breakages are a smaller issue, but it isn't nice anyway.

Of course, breakage is never nice.

> CI is limited and it blocks other PRs.

Well, so is my time and resources (for reference: a lot of these PRs are coming from a Pinebook Pro, clean builds of these packages take quite a while and drain the battery considerably, half an hour and 10% battery for topgrade for example). waiting a bit until CI has run through doesn't block the workflow usually, building the packages locally is more overhead IMO.

Would integrating sccache into rust packages in xbps-src be accepted upstream? That would make it easier for me to test the packages locally. Would be optional of course, behind an env var or something like that.