| 1 |
Boyd Stephen Smith Jr. napisał(a): |
| 2 |
> |
| 3 |
> e.g.: |
| 4 |
> $ grep KEYWORD beryl-plugins-0.1.3.ebuild |
| 5 |
> KEYWORDS="~amd64 ~ppc ~ppc64 ~x86" |
| 6 |
> |
| 7 |
> So, you can simply find the KEYWORDS variable in the ebuild you are trying |
| 8 |
> to use and add one of those keywords to your package.keywords. Of course, |
| 9 |
> if you do anything other than ~${ARCH}, where ${ARCH} is your current |
| 10 |
> architecture and it breaks, you get to keep both pieces. |
| 11 |
> |
| 12 |
|
| 13 |
To my surprise, the output is: |
| 14 |
|
| 15 |
KEYWORDS="" |
| 16 |
|
| 17 |
There are... No keywords? I'm puzzled. I'm using x86 architecture. |
| 18 |
Should I then edit the ebuild and manually add my arch to KEYWORD |
| 19 |
variable? I'm just guessing - maybe it will help somehow. |
| 20 |
|
| 21 |
Regards, |
| 22 |
Jan Stępień |
| 23 |
|
| 24 |
-- |
| 25 |
Mail jan at stepien com pl |
| 26 |
Jabber jano at jabber aster pl |
| 27 |
GG 1894343 |
| 28 |
Web http://stepien.com.pl |
Archives