| 1 |
Am 17.02.2014 22:44, schrieb David James: |
| 2 |
|
| 3 |
|
| 4 |
> From a theoretical perspective, the reason why I implemented this is |
| 5 |
> because "ebuilds" are the source of truth. According to the ebuilds, the |
| 6 |
> owner repo of dev-libs/C-1 is repo1, so this means that, with --newrepo, |
| 7 |
> any binpkg for dev-libs/C-1 from repo2 would be invalid. |
| 8 |
|
| 9 |
Actually this test passes even without --new-repo. So yes, your |
| 10 |
interpretation is what's used by portage. Patch is committed. |
| 11 |
|
| 12 |
> |
| 13 |
> This functionality is useful in the case where an ebuild changes repos. |
| 14 |
> In this case, with --newrepo, you would want the package to be rebuilt |
| 15 |
> and any binaries to be invalidated, and our tests validate this. |
| 16 |
> |
| 17 |
> Cheers, |
| 18 |
> |
| 19 |
> David |
| 20 |
> |
Archives