| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Ned Ludd wrote: |
| 5 |
>> Please invert the logic so that rather than changing default behavior |
| 6 |
>> you add a new option choose the types of deps to include. |
| 7 |
|
| 8 |
Can you explain how my proposed change in the default behavior of --usepkg is going to hurt things? The current default behavior is inconsistent because build time dependencies are considered for packages that are installed but not for binary packages that are about to be installed. By doing away with this one special case for binary packages, the dependency calculation will be consistent for installed vs. binary packages. |
| 9 |
|
| 10 |
>> I was in favor and thought we were going to do it after 2.1 and the 2006 |
| 11 |
>> release under the idea of the variable ACCEPT_DEPENDS |
| 12 |
> |
| 13 |
>> export ACCEPT_DEPENDS="DEPEND RDEPEND PDEPEND" |
| 14 |
>> emerge -K system |
| 15 |
|
| 16 |
While I admire the flexibility of your ACCEPT_DEPENDS proposal, I feel that it exposes far too much complexity to the user. Eventually, the functionality of emerge will be available as part of the portage api and people will probably be able to exploit it to do all kinds of crazy things like that. I just don't feel that it's appropriate to expose something like that through the emerge interface. Can you explain why we should expose that much complexity through the emerge interface? |
| 17 |
|
| 18 |
>> Whatever we do in the end does not really matter as long |
| 19 |
>> as we don't change default expected behaviors. |
| 20 |
|
| 21 |
Again, can you explain how my proposed change is going to hurt things? |
| 22 |
|
| 23 |
Zac |
| 24 |
|
| 25 |
-----BEGIN PGP SIGNATURE----- |
| 26 |
Version: GnuPG v1.4.4 (GNU/Linux) |
| 27 |
|
| 28 |
iD8DBQFEtRPH/ejvha5XGaMRAkICAKCutrtehYGHyHN+UQUDjTRvUWxDqwCff4Fv |
| 29 |
6Z2UUrFPD4UP9aCD2QHi2XM= |
| 30 |
=tRS4 |
| 31 |
-----END PGP SIGNATURE----- |
| 32 |
-- |
| 33 |
gentoo-portage-dev@g.o mailing list |
Archives