I didn't have zope or zope-config installed. zope needs zope-config because it runs zope-config at the end of the ebuild. But if you try to emerge zope-config, it wants to emerge zope first, thus causing the execution of /usr/sbin/zope-config to fail when emerging zope: /usr/sbin/ebuild.sh: line 144: /usr/sbin/zope-config: No such file or directory The only way I can think of fixing this is to make zope-config NOT depend on zope?
re-assign to net-zope@gentoo.org
this has always been working this way, what zope version did you try to install?
Let me clarify what I did. I did emerge -vp zope-config and portage wanted to merge zope first, and then zope-config. I then did "emerge zope-config". The zope install didn't work 100% because zope-config is missing. I think this is what we need: zope should have a DEPEND on zope-config zope-config should have an RDEPEND on zope, but no DEPEND on zope
what zope version did you try to install?
the stable one, 2.6.1
> zope should have a DEPEND on zope-config > zope-config should have an RDEPEND on zope, but no DEPEND on zope this is the current situation I think it is a portage bug since it handles DEPEND and RDEPEND the same way
how would you expect them to be handled ?
zope-config should be emerged first since there is a DEPEND on it in zope, then zope should be merged since there is a RDEPEND on it in zope-config
can't you use PDEPEND in zope-config as a workaround ? DEPEND and RDEPEND have the same priority, the only difference is that DEPEND is ignored for .tbz2 packages. Not rejecting this request, but it could be problematic to implement.
I think PDEPEND is exactly what we need here, fixed in zope-config.
