| 1 |
On Thu, Apr 11, 2013 at 01:39:31PM -0400, Rick "Zero_Chaos" Farina wrote: |
| 2 |
> > For example, sys-devel/gcc lists: |
| 3 |
> > |
| 4 |
> > RDEPEND: sys-libs/zlib virtual/libiconv >=dev-libs/gmp-4.3.2 |
| 5 |
> > >=dev-libs/mpfr-2.4.2 >=dev-libs/mpc-0.8.1 |
| 6 |
> > |
| 7 |
> > I'd like it to list: |
| 8 |
> > |
| 9 |
> > RDEPEND: =sys-libs/zlib-1.2.7 =virtual/libiconv-0 |
| 10 |
> > =dev-libs/gmp-5.0.2_p1 =dev-libs/mpfr-3.1.1 =dev-libs/mpc-1.0.1 |
| 11 |
> |
| 12 |
> This is called EAPI 5 subslots. it should not be addressed in catalyst |
| 13 |
> nor portage, things should simply set subslot deps properly. |
| 14 |
|
| 15 |
I had understood sub-slotting to be a way to list the ABI provided by |
| 16 |
a given package (in SLOT) or required by a given package (in *DEPEND), |
| 17 |
not a way for a package to record which ABIs it was built against. |
| 18 |
For example, GCC builds against >=dev-libs/mpc-0.8.1, but there are |
| 19 |
some incompatible ABIs in that range. We need to know which ABI the |
| 20 |
built package actually uses, not which ABIs it could have used. |
| 21 |
|
| 22 |
In any case, we probably still need a warning somewhere though, since |
| 23 |
I don't foresee GCC moving to EAPI 5 in the near future ;). I'm |
| 24 |
working up a patch with comre comments in files/catalyst.conf. |
| 25 |
|
| 26 |
Cheers, |
| 27 |
Trevor |
| 28 |
|
| 29 |
-- |
| 30 |
This email may be signed or encrypted with GnuPG (http://www.gnupg.org). |
| 31 |
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy |
Archives