On Tue, Feb 26, 2013 at 8:20 AM, Brian Dolbec <[email protected]> wrote: > --- a/doc/catalyst-spec.5.txt > +++ b/doc/catalyst-spec.5.txt > @@ -138,9 +138,19 @@ it should update the seed stage or not (valid values: > `yes no`). > *update_seed_command*:: > This is an optional command to pass to emerge for updating the seed > stage (example: `--update dev-libs/mpfr dev-libs/mpc dev-libs/gmp`) > -If not specified, catalyst will update gcc deps. > +If not specified, catalyst will update gcc's deps, and rebuild gcc if any of > +it's deps are updated with a new version. Even if it itself is not updated. > +This prevents gcc breakage when it's dependency lib sonames have changed. > This setting requires enabling update_seed. > > +*update_seed_system*:: > +This is an optional setting supported by stage1 to tell catalyst if > +it should update the seed's system packages or not (valid values: `yes no`). > +This is run after any update_seed_command, updating any remaining upgradable > +system packages. > +This setting requires enabling update_seed.
I don't see any need for an update_seed_system option. If someone wants to run emerge @system then they can do: update_seed_command: --options @system
