Eli Schwartz wrote:
> On 7/13/24 8:42 AM, Peter Humphrey wrote:
>> Hello list,
>>
>> Where I live, updates to portage itself usually take longer to appear as a
>> binary package than as source, so I can't 'getbinpkg'. Therefore I've set:
>>
>> # cat /etc/portage/env/nobinpkg.conf
>> FEATURES="${FEATURES} -getbinpkg"
>>
>> # cat /etc/portage/package.env
>> sys-apps/portage nobinpkg.conf
>>
>> But still portage wants to fetch the binary.
>>
>> What am I doing wrong?
> As a matter of curiosity, why do you need to do any such thing at all?
>
> If there is no binary package available for portage yet, then portage
> will automatically build it from source instead, which is exactly what
> setting -getbinpkg for it would do. So why bother?
>
> The only thing that setting -getbinpkg could do is prevent you from
> using a binary on the off chance that it happens to appear faster for you.
>
>
> Note that independent of whether it's useful to exclude this one
> package, the functionality doesn't work. You cannot set per-package
> getbinpkg, this is tracked as https://bugs.gentoo.org/463964
>
>
> -- Eli Schwartz
That's actually why he wants to do that. It seems for some reason,
portage shows up as a source long before the binary packages do. So, he
wants to make a exception for portage so he can just build it himself
locally. Given it likely doesn't take long to build from source anyway,
why not. I'd suspect tho that most packages show up as source before
binary packages do tho. After all, one has to have the source to build
the binary ones. I guess maybe portage lags behind further than others
or something, at least for the OP anyway.
I never did the binary thing tho. When compiles start taking to long,
time to build a faster rig. :-D Some devices tho, like Raspberry Pis,
don't have that option.
Dale
:-) :-)
