Soo… say I have a couple ebuilds that are probably not great quality (approximately first ones I wrote), but work. How should I go about making these useful for other people? Perhaps even including them in the main gentoo repo? This is mostly about Request Tracker, which already is in the repo, albeit in an old version (and with a wrong makefile patch), plus some of it’s dependencies (some of which I updated, some that never were in the main repo).

#Gentoo

I would like to tap into the #Gentoo Fediverse mind pool one more time if I could have some advice.

I am currently on the Gentoo-dist bin kernel and would like start compiling and customizing my own kernel, but I have never done anything like that before.

So here are my questions:

- What is the best way to start?
- Are there any good tools/scripts/etc that I should use?
- Is there anything I could/should do to protect myself for goofing up?

Thank you for your time!

Am I missing something or is it basically impossible to have `cargo update` actually select dependencies that are acceptable for the specific minimal `rust-version`? Like, even if you install old #RustLang version, `cargo update` from this version will update `Cargo.lock` to dependencies that require a newer Rust version and render the package non-buildable?

So yeah, I suppose you either end up requiring newer Rust (but you don't really know which version, since you don't know what's the highest minimal requirement in your dependencies), or you update `Cargo.lock` by hand. Such a great tooling!

https://github.com/samuelcolvin/watchfiles/pull/267#issuecomment-2094753389

#Gentoo

Update PyO3 by mgorny · Pull Request #267 · samuelcolvin/watchfiles

Update PyO3 using cargo update. This is the minimal change needed to address #261.

^GitHub