On Fri, 2003-12-05 at 23:43, Spider wrote: > > > Why isn't this a DEPEND then? *smacks* :) > > > > Apparently, it is not a depend in order to avoid a circular > > dependency. > > > > Weird, but reasonable.. Couldn't it just be a block on older versions?
I could, except it is not that obvious to the user what he/she should do
with the block. For instance, if I add that DEPEND, it would say:
bash-2.05b# emerge -p python
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[blocks B ] <sys-apps/portage-2.0.49-r16 (from pkg
dev-lang/python-2.3.2-r2)
[ebuild N ] dev-lang/python-2.3.2-r2
Luckily, portage is smart enough not to allow anyone unmerging portage
itself (phew!). Except, that if you do:
bash-2.05b# emerge -up portage
...
[blocks B ] <sys-apps/portage-2.0.49-r16 (from pkg
dev-lang/python-2.3.2-r2)
[ebuild N ] dev-lang/python-2.3.2-r2
[ebuild U ] sys-apps/portage-2.0.49-r18 [2.0.49-r10]
Which is rather unintuitive in itself, and there lies the circular
dependency, even though we've effectively avoided portage from detecting
a circular dep.
The solution is to do "emerge portage" instead, but that is also not
obvious from the output, at least to me. Anyone thinks that putting
<sys-apps/portage-2.0.49-r16 would be more intuitive to the user than
actually checking that in pkg_setup()?
Cheers,
--
Alastair 'liquidx' Tse
>> Gentoo Developer
>> http://www.liquidx.net/ | http://dev.gentoo.org/~liquidx/
signature.asc
Description: This is a digitally signed message part
