On Sun, Dec 4, 2011 at 9:35 PM, Sven Vermeulen <email@example.com> wrote:
> The dependency must be on both levels, because the SELinux module must be
> installed before the package is installed (and in theory, RDEPEND could
> trigger an installation afterwards): during the installation phase, Portage
> labels the files on the system (which would get wrong labels if the module
> isn't installed yet). Also, DEPEND isn't sufficient due to binary package
> support requirements.
> Sven Vermeulen
>  I am aware that Portage currently installs RDEPEND before the package
> itself, but that might change in the future and other package managers might
> exhibit different behavior.
I haven't really understood what you mean with RDEPENDs being scheduled "after".
RDEPEND must be always scheduled before the pkg requiring it, changing
this behaviour would have disruptive effects on all the PMS out there
(OTOH I think I haven't gotten the point actually?). I guess portage
may schedule it in arbitrary order if the RDEPEND dep itself is
satisfied already (this would mean that you explicitly pulled it in),
and this is the only case I can think of.
If you need to schedule a dep install at some point, you should rather
use PDEPEND, but if the same is required earlier in the schedule,
well, you're flooked.