News:Kits Are Go (And Ego Needs a Manual Bump)
Kits Are Go (And Ego Needs a Manual Bump)
An update on kits and how to manually update to ego-1.1.3-r3 (required steps for some)By Drobbins / August 17, 2017
Please make sure you have updated to ego-1.1.3-r3 or later. Manual steps may be required if you have version 1.1.3 through 1.1.3-r2 which need manual intervention.
It's time to provide an update on kits. Overall, things have been going very well with kits and the transition has been successful. One snag is that if you have installed Package:Ego 1.1.3 through 1.1.3-r2, you will need to manually update your meta-repo using the following steps and install Package:Ego 1.1.3-r3 or later as follows:
# cd /var/git/meta-repo # git pull # git submodule init # git submodule update # emerge -1 egoNew features in ego-1.1.3-r3 include the ability for ego to determine if it needs to upgrade prior to updating meta-repo. It will fetch a file called
DEPENDfrom meta-repo and determine if requirements are met. If they are not, it will prompt you to perform the necessary upgrades to your system before proceeding to update meta-repo. This will allow the easy roll-out of new functionality to new users.
Boot-Update and Intel Microcode
Please note that boot-update has been upgraded so that if you have an Intel system and use GRUB 2, boot-update will automatically upgrade your CPU's intel microcode at boot time. To enable this, ensure you have the latest boot-update installed and re-run
boot-update. If you see any error messages when this happens, re-emerge boot-update to resolve any dependency issues.
Upcoming functionality in Funtoo will require ego-1.1.3-r3 or later, so make sure you update as soon as possible so that you are ready for the following features:
- Python 3.6 support
- new kits code allows dynamic switching of python-kit from 3.4-prime to master, which will allow seamless transition to python-3.6 for those who need it. This required significant enhancement of the ports system and
eproplays a critical role in de-coupling python from the rest of the system and allowing everything to just work.
- Migration away from submodules
- To allow users to more easily switch branches, it is very likely that we will be moving away from submodules for kits and instead have ego manage the git repositories directly. This will provide a lot more flexibility than is currently available, as it is currently tricky for users to shift away from our prime kits.
- New kit maintainers/curators
- As we grow, I will be looking for developers to maintain specific kits and help to ensure that prime branches offer a seamless experience for users. I will also be looking to add new revisions of existing branches for various kits, such as xorg-1.1.9 and others.