On 19 Jun 2001, Warly wrote:
> > In the old days, most of these packages only had a foo and a foo-devel
> > package. Now there usually is foo, libfoo0 and libfoo0-devel with
> > "foo requires libfoo0 = 1.2.3", "libfoo0-devel requires libfoo0 = 1.2.3"
> > and possibly some "bar-2.3.4 requires libfoo0". When you get foo-2.0.0,
> > you can install libfoo2 and upgrade foo and libfoo-devel without having
> > to rebuild or even port bar.
> > However, it can be assumed that foo-2.0.0 and foo-1.2.3 can not be installed
> > at the same time, so if libfoo0 requires foo-1.2.3, you cannot have
> > foo-2.0.0 and bar-2.3.4 at the same time, which is bad.
>
> libfoo0 must not require foo, or it is an error
Currently libGConf1 requires GConf1 and it's intentional.
Abel
