Re: [gentoo-user] Eliminating unwanted linux-firmware blobs.

2024-06-28 Thread Vitaliy Perekhovy
On Fri, Jun 28, 2024 at 04:17:23PM -, Grant Edwards wrote:
> Is there any graceful way to handle the elimination of unwanted
> linux-firmware blobs when doing an update?
> 
> I believe I understand the process as outlined at
> https://wiki.gentoo.org/wiki/Linux_firmware:
> 
>  1. install/upgrade sys-kernel/linux-firmware
>  2. edit /etc/portage/savedconfig/sys-kernel/linux-firmware-ddmm
>  3. re-emerge sys-kernel/linux-firmware with the savedcofnig USE flag
> 
> I've tried that a few times, but it's rather annoying to have to do
> that every time linux-firmware gets updated.
> 
> AFAICT, the list of three or four blobs that I actually need on a
> specific machine never changes.
> 
> It seems like there ought to be a way to configure that required
> firmware list and have the emerge -u "just work", but I can't find
> it. Have I missed something?
> 
> Yes, I know...
>   Disk space is cheap.
>   Premature optimization ...
>   etc.
> 
> It still annoys me.
> 
> --
> Grant

Save your firmware list in /etc/portage/savedconfig/sys-kernel/linux-firmware
That's it.

-- 
Best regards,
Vitaliy Perekhovy


signature.asc
Description: PGP signature


Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-15 Thread Vitaliy Perekhovy
On Fri, Jun 14, 2024 at 04:54:09PM -0400, Jack wrote:
> I don't have any such directory.  What package does it belong to, or is  
> it a config setting for portage or another package?

Yes, it is a configuration of portage itself. There is an env variable
CONFIG_PROTECT that contains a list of directories that portage will
protect from automatic modification. Please check this article:
https://wiki.gentoo.org/wiki/CONFIG_PROTECT

You can query that variable by `portageq envvar CONFIG_PROTECT'.

-- 
Regards,
Vitaliy Perekhovy


signature.asc
Description: PGP signature


Re: [gentoo-user] Difficulty with updating /etc/basb/bashrc

2024-06-14 Thread Vitaliy Perekhovy
On Fri, Jun 14, 2024 at 03:53:35PM +, Alan Mackenzie wrote:
> I think portage is at fault here - it should retain the older standard
> version of /etc/bash/bashrc so that users can resolve the differences
> with a 3-way diff.

Before replace your old bashrc file, portage place the old one
here: /etc/config-archive/etc/bash/bashrc

-- 
Regards,
Vitaliy Perekhovy


signature.asc
Description: PGP signature


Re: [gentoo-user] Emerge -K ignoring new packages

2023-11-20 Thread Vitaliy Perekhovy
On Mon, Nov 20, 2023 at 05:07:45PM +, Peter Humphrey wrote:
> Hello list,
> 
> Now that I have my NFS set up (with help - thanks) the next problem is that, 
> having new packages built by my workstation over NFS, emerge on the tiny box 
> is ignoring all those new packages. And yes, I have checked that they do 
> exist, and in the right place: /var/cache/packages/ .
> 
> The man page says that any new package will cause a remerge, so what has 
> tripped me up this time?
> 
> -- 
> Regards,
> Peter.
> 
> 
> 
> 

Default location for binary packages is /var/cache/binpkgs/

-- 
Regards,
Vitaliy Perekhovy


signature.asc
Description: PGP signature