this post was submitted on 04 May 2025
378 points (98.5% liked)
linuxmemes
27360 readers
990 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
3. Post Linux-related content
sudo
in Windows.4. No recent reposts
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Or set up your own binhost
I think that's more for when you have multiple machines (that would use the same USE flags) and you only want to have to compile once. OP's use-case re: binary packages would be more about getting them from somebody else (i.e. a public binhost that already exists) so he doesn't have to compile at all.
I was suggesting using your own binhost as an alternative to distcc.
If someone's considering distcc, presumably they've already decided not to use the public Gentoo binaries, and want to do the compilation themselves
One issue with distcc is some of the build operations can't be delegated. If you want to minimise resource usage as much as possible (e.g. on old hardware) and want to compile yourself, then running your own binhost makes sense.