if A needs to be downloaded then all dependencies of A should be be available too (let's say B gets build, then A depending on B, B gets updated again and the old build deleted. Now there is only A and B waiting to get built.. downloading A alone would be a mistake)
if A needs to be downloaded but there are still packages queued that depend on A we should at least warn (let's say we update Python and some Python package but only Python is built yet. Since there is an ABI/API beak we'd need to wait for all depending packages to get rebuilt). I'd say abort and add a "--ignore-rdeps=" flag to skip it
if A needs to be downloaded then all dependencies of A should be be available too (let's say B gets build, then A depending on B, B gets updated again and the old build deleted. Now there is only A and B waiting to get built.. downloading A alone would be a mistake)
if A needs to be downloaded but there are still packages queued that depend on A we should at least warn (let's say we update Python and some Python package but only Python is built yet. Since there is an ABI/API beak we'd need to wait for all depending packages to get rebuilt). I'd say abort and add a "--ignore-rdeps=" flag to skip it