| 1 |
Brian Harring wrote: |
| 2 |
> |
| 3 |
> So why abuse keywords for it, when restrict exists? Keywords has a |
| 4 |
> specific purpose now, it's not used to store bools for random |
| 5 |
> capabilities (one could argue that archs are just that, but that's a |
| 6 |
> bit of a reach). |
| 7 |
> |
| 8 |
> That said, RESTRICT *is* used to store random bools for capabilities; |
| 9 |
> why do you think keywords should be adjusted in scope when RESTRICT |
| 10 |
> has historically served as a dumping ground for bits like this? |
| 11 |
> |
| 12 |
> ~harring |
| 13 |
|
| 14 |
Is it needed to state cross from host to target? If so then restrict |
| 15 |
isn't enough. It's one of those fun cases where we wonder if anyone |
| 16 |
will actually test and compute the functionality of host to target and |
| 17 |
use it; or if it's not really needed (something either compiles for all |
| 18 |
cross arches or none). I'd prefer the former, but then it's a mapping |
| 19 |
of host -> target booleans, not just 1 boolean. |
| 20 |
|
| 21 |
-- |
| 22 |
gentoo-portage-dev@g.o mailing list |
Archives