On Friday, 12 June 2020 15:52:50 BST Michael wrote:
> On Friday, 12 June 2020 15:44:05 BST n952162 wrote:
> > And, BTW, is there a reason to do @system if that's a subset of @world?
>
> To rebuild with the latest gcc and work through any convoluted dependencies
> cutting across into world. It may not add anything, but other than
> rebuilding a few packages I don't think it will hurt.
Here's the pair of scripts I use when upgrading gcc:
$ cat /usr/local/bin/ejsys
#!/bin/bash
echo && echo "Be sure to have upgraded gcc and switched to the new version!"
&& echo
echo "Mounting /boot for intel-microcode to install." && echo
mount /boot
emerge $@ -1 --jobs libtool && emerge $@ -1 --jobs llvm clang wxGTK &&\
emerge $@ --jobs --keep-going --nospinner @system linux-firmware intel-
microcode \
--exclude="gcc libtool llvm clang wxGTK"
$ cat /usr/local/bin/ejeworld
#!/bin/bash
emerge -1 --jobs --load-average=48 --keep-going --nospinner $@ \
-e @apps @base @core @plasma @utils @xorg @world \
--exclude="$(cat ~/system.pkgs) linux-firmware intel-microcode \
libtool llvm clang wxGTK gentoo-sources"
First I run ejsys, then I compile a new kernel and boot it, then I run
ejeworld.
The precise choice of packages to emerge with @system may differ between
systems.
HTH.
--
Regards,
Peter.
