| 1 |
On 03/05/2017 02:12 PM, Zac Medico wrote: |
| 2 |
> |
| 3 |
> Incorrect. |
| 4 |
> |
| 5 |
> ... |
| 6 |
> |
| 7 |
> Incorrect. |
| 8 |
> |
| 9 |
|
| 10 |
I see my mistakes, but maintain that this is confusing =) |
| 11 |
|
| 12 |
|
| 13 |
> |
| 14 |
> The --with-bdeps-auto option results in desirable behavior by default, |
| 15 |
> and it's also backward compatible with existing --with-bdeps and |
| 16 |
> --usepkg usage. It just does the right thing, minimizing the impact to |
| 17 |
> existing emerge usage. |
| 18 |
|
| 19 |
I was hoping that since nothing breaks with --update-bdeps=y and |
| 20 |
--clean-bdeps=n (the new defaults), we could just disable --with-bdeps |
| 21 |
immediately and emit a warning when it's given. |
| 22 |
|
| 23 |
|
| 24 |
> |
| 25 |
> There some problems with --update-bdeps/--clean-bdeps: |
| 26 |
> |
| 27 |
> * The program logic will be more complicated, since --with-bdeps will |
| 28 |
> have to override both options for backward-compatibility with existing |
| 29 |
> --with-bdeps usage. |
| 30 |
|
| 31 |
Not applicable if --with-bdeps goes away. |
| 32 |
|
| 33 |
|
| 34 |
> * The meaning of --clean-bdeps is confusing. Does --clean-bdeps=y mean |
| 35 |
> to clean build time deps, or does it mean to pull build time deps into |
| 36 |
> the dependency graph for removal operations? |
| 37 |
|
| 38 |
--clean-bdeps means clean the bdeps. |
| 39 |
|
| 40 |
|
| 41 |
I totally agree that the worst option of all is to keep --with-bdeps AND |
| 42 |
introduce the other two. |
Archives