| 1 |
On Sun, Jun 12, 2011 at 02:13:35AM -0700, Zac Medico wrote: |
| 2 |
> On 06/12/2011 01:18 AM, Ulrich Mueller wrote: |
| 3 |
> >>>>>> On Sun, 12 Jun 2011, Michał Górny wrote: |
| 4 |
> > |
| 5 |
> >> True. How about pkg_setup()? Shall we assume RDEPEND are there or |
| 6 |
> >> rely on @system only? |
| 7 |
> > |
| 8 |
> > IIUC, with Portage's breaking of dependency cycles there's no absolute |
| 9 |
> > guarantee that packages in RDEPEND will be available in pkg_*. |
| 10 |
> |
| 11 |
> It would be more accurate to say that it's guaranteed except for cases |
| 12 |
> in which circular dependencies make it impossible to guarantee. |
| 13 |
|
| 14 |
Those instances shouldn't be just dropped by the manager; a |
| 15 |
--force-break-ebuild-rules option for those cases is one thing, same |
| 16 |
for attempting multiple merge/replace to break a use cycle. |
| 17 |
|
| 18 |
But if it just says "meh" to a cycle... that's wrong. |
| 19 |
|
| 20 |
Under what scenarios will it pull that? |
| 21 |
~brian |
Archives