On Thursday 25 February 2010 04:03:16 Jeroen Roovers wrote: > Hello developers, > > this has annoyed me for a long time. > > restore_config() dies when it cannot find a saved config file, while > later on in any ebuild that uses savedconfig.eclass, it will save the > config file anyhow. That means it will not use an edited saved config > file during the first emerge, which is to be expected and should not be > fatal. > > The current forces you to emerge the same ebuild twice using _different_ > USE flags to achieve anything: > > 1. USE="-savedconfig" emerge cat/foo > 2. $EDITOR /etc/portage/savedconfig/cat/foo > 3. USE="savedconfig" emerge cat/foo > > This is quite illogical.
Fixing this is fine my me. Daniel (illogical savedconfig.eclass author)
