| 1 |
On Sat, Aug 13, 2011 at 7:21 AM, Robin H. Johnson <robbat2@g.o> wrote: |
| 2 |
> On Sun, Aug 07, 2011 at 01:50:42PM +0200, Raúl Porcel wrote: |
| 3 |
>> With subprofiles we could keyword such packages, mask them globally on |
| 4 |
>> arm and unmask it on the subprofile of the subarchitecture that supports it. |
| 5 |
> I suggest you go and look at the solution that was in place for MIPS |
| 6 |
> subarches as well to take that into consideration. |
| 7 |
> |
| 8 |
> I think it still exists in: mips-sources, arcboot, arcload. |
| 9 |
> The latter two being bootloaders that need to be specifically configured |
| 10 |
> for the subarch else they just don't work. |
| 11 |
|
| 12 |
We did have that, but I removed it because the profiles weren't |
| 13 |
maintained. On MIPS, the purpose was to simply prevent things like |
| 14 |
arcload from being installed on systems where arcload doesn't |
| 15 |
work/isn't useful, which is only minimally useful itself. |
| 16 |
|
| 17 |
ARM seems to have a much better reason for doing this -- packages |
| 18 |
won't even compile on some subarchs. |
| 19 |
|
| 20 |
Matt |
Archives