| 1 |
Martin Vaeth <martin <at> mvath.de> writes: |
| 2 |
|
| 3 |
|
| 4 |
> >> > # PORTAGE_PROFILE=/usr/portage/profiles/arch/arm/armv7a/eapi |
| 5 |
|
| 6 |
> >> This is not a directory. [...] |
| 7 |
|
| 8 |
> > How do I determine [...] |
| 9 |
|
| 10 |
> Choose the directory to which you would put the symlink |
| 11 |
> (I suppose ..../armv7a in this example). |
| 12 |
|
| 13 |
|
| 14 |
|
| 15 |
|
| 16 |
# PORTAGE_PROFILE=/usr/portage/profiles/arch/arm/armv7a eix -c --system |
| 17 |
No matches found. |
| 18 |
|
| 19 |
|
| 20 |
Surely I'm not the first person curious about the default or other |
| 21 |
profile listing of packages for @system on different architectures? |
| 22 |
|
| 23 |
I've tried all sort of command syntax and manually parsed up and down |
| 24 |
these directories. |
| 25 |
|
| 26 |
Pick any embedded arm profile and *please* show me the syntax to |
| 27 |
determine the @system packages to be installed associate with any |
| 28 |
embedded arm profile? |
| 29 |
|
| 30 |
please? |
| 31 |
|
| 32 |
James |
Archives