cmake is not downloaded as binary. Your system has built it and stored the binaries it built, especially if more than one package is like that.
This happens when you use quickpkg or emerge -b. I seem to recall there is a global option that can be used for this, I used it one when building on a central host to then distribute binaries to other hosts. Alan On Thu, Sep 28, 2023 at 5:29 PM n952162 <n952...@web.de> wrote: > Hello, > > When I do: > > $ equery list cmake > * Searching for cmake ... > [IP-] [ ] dev-util/cmake-3.22.2:0 > > Furthermore, I find no /var/tmp/portage/dev-util/cmake* > > and when I do this: > > $ cd /var/cache/binpkgs/dev-util > > $ tar -tjvf cmake-3.22.2.tbz2 2>&1 | grep /usr/bin/cmake > -rwxr-xr-x root/root 7332776 2022-03-03 10:10 ./usr/bin/cmake > > I see that a ready-to-use cmake is included. > > Am I interpreting this correctly that cmake is downloaded as pre-built > binary? > > Can I inhibit that? How many pre-built binaries do I have? How do I > get rid of them? > > Incidently, I checked another package in /var/cache/binpkgs, byacc, and > it's the same. > > > > -- Alan McKinnon alan dot mckinnon at gmail dot com
