On Thu, Apr 11, 2013 at 01:39:31PM -0400, Rick "Zero_Chaos" Farina wrote:
> > For example, sys-devel/gcc lists:
> > 
> >   RDEPEND: sys-libs/zlib virtual/libiconv >=dev-libs/gmp-4.3.2
> >     >=dev-libs/mpfr-2.4.2 >=dev-libs/mpc-0.8.1
> > 
> > I'd like it to list:
> > 
> >   RDEPEND: =sys-libs/zlib-1.2.7 =virtual/libiconv-0
> >     =dev-libs/gmp-5.0.2_p1 =dev-libs/mpfr-3.1.1 =dev-libs/mpc-1.0.1
> 
> This is called EAPI 5 subslots.  it should not be addressed in catalyst
> nor portage, things should simply set subslot deps properly.

I had understood sub-slotting to be a way to list the ABI provided by
a given package (in SLOT) or required by a given package (in *DEPEND),
not a way for a package to record which ABIs it was built against.
For example, GCC builds against >=dev-libs/mpc-0.8.1, but there are
some incompatible ABIs in that range.  We need to know which ABI the
built package actually uses, not which ABIs it could have used.

In any case, we probably still need a warning somewhere though, since
I don't foresee GCC moving to EAPI 5 in the near future ;).  I'm
working up a patch with comre comments in files/catalyst.conf.

Cheers,
Trevor

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy