Updating portage gentoo

24-Feb-2020 22:22

The content of this file is the name of the profile that should be "upgraded to"; portage uses this information to automatically warn you when you should update to a new profile.There are various reasons that a new profile may be created: the release of new versions of core packages (such as ) that are incompatible with previous versions, a change in the default USE flags, or in the virtual mappings, or maybe a change in system-wide settings (such as defining udev to be the default manager for Keeping up with new releases Releases without profile changes If a new Gentoo release is announced that does not include a new profile (such as the 2004.1 release for x86), then you can safely pretend that it never happened :).If you decide to migrate to the new profile, then you will have to manually perform the update.The way you update may vary significantly from release to release; it depends on how deep the modifications introduced in the new profile.From the beginning, Gentoo was designed around the concept of fast, incremental updates.Ideally, you install once and then do not to bother with releases: just follow the instructions in A Portage Introduction in the Gentoo Handbook that explain how to keep your system up to date.You can also find these instructions at the end of this guide.Supported profiles The following profiles are officially supported by Gentoo developers: value, and is only relevant for those who have not installed an X server yet.

You know (being a Gentoo user after all) that this process is extremely frustrating for power users that want to live on the bleeding edge.I'm just starting out with Gentoo and I'm getting a bit stuck installing programs with Portage. Many of the programs I try to install (git, gedit, chrome, nautilus) eventually depend on pth, whatever that is. * The ebuild environment file is located at '/var/tmp/portage/dev-libs/pth-2.0.7-r3/temp/environment'.But it fails with an econf error: ERROR: dev-libs/pth-2.0.7-r3::gentoo failed (configure phase): econf failed Call stack: ebuild.sh, line 93: Called src_configure environment, line 2881: Called econf '--disable-static' phase-helpers.sh, line 577: Called die The specific snippet of code: die "econf failed" If you need support, post the output of `emerge --info '=dev-libs/pth-2.0.7-r3::gentoo'`, the complete build log and the output of `emerge -pqv '=dev-libs/pth-2.0.7-r3::gentoo'`. [ ok ] * Replacing obsolete head/tail with POSIX compliant ones * - fixed aclocal.m4 * - fixed configure * Running elibtoolize in: pth-2.0.7/ * Applying portage/1.5.10 patch ... ) is a Linux distribution built using the Portage package management system.