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