| 1 |
maillog: 07/12/2004-23:36:49(+0000): Ferris McCormick types |
| 2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 3 |
> Hash: SHA1 |
| 4 |
> |
| 5 |
> On Wed, 8 Dec 2004, Georgi Georgiev wrote: |
| 6 |
> |
| 7 |
> >maillog: 08/12/2004-07:52:19(+0900): Georgi Georgiev types |
| 8 |
> >>maillog: 07/12/2004-19:59:05(+0000): Ferris McCormick types |
| 9 |
> >>>6. NOTE: The two 'is_kernel' tests produce error messages, but (for me, |
| 10 |
> >>> at any rate) ebuild operation is correct anyway. I have not |
| 11 |
> >>> investigated further, but as I recall, the messages were: |
| 12 |
> >>> [: wrong number of arguments (for the check kernel-2.2.x) |
| 13 |
> >>> Command '*' not understood |
| 14 |
> >> |
| 15 |
> >>This is what I had in my overlay while testing the ebuild yesterday. |
| 16 |
> >>The linux-info.eclass kernel_is() should only return an exit code so its |
| 17 |
> >>output should not be looked at. I.e. those "[" and "$(" are not needed. |
| 18 |
> > |
| 19 |
> >Ah, well, linux-info broke in the meantime, that's all. |
| 20 |
> > |
| 21 |
> |
| 22 |
> Thanks for the information. For your confusion, there is a 'kernel_is' |
| 23 |
> in linux-info.eclass, and an 'is_kernel' in x11.eclass. The ebuilds |
| 24 |
> used to use is_kernel; now they use kernel_is, and perhaps the |
| 25 |
> difficulties started with that? |
| 26 |
|
| 27 |
is_kernel will probably dissapear soon enough. |
| 28 |
|
| 29 |
And to the attention of spyderous: kernel_is from linux-info returns a |
| 30 |
valid exit code and outputs lots of einfos, therefore the [ $(kernel_is |
| 31 |
..) ] and the other $(kernel_is) must not be in a subshell whose output |
| 32 |
is passed to the command line (hence the "Command '*' not understood"). |
| 33 |
|
| 34 |
And lastly, well, sorry for the misinformation. linux-info did indeed |
| 35 |
break, but only for me I guess (am I the only one using KERNEL_OUTPUT, |
| 36 |
because nobody else seems to complain when stuff related to |
| 37 |
KERNEL_OUTPUT is obviously broken), which was unrelated to the current |
| 38 |
problem. It's just that when I tried it, there were two problems to |
| 39 |
solve. |
| 40 |
|
| 41 |
-- |
| 42 |
\/ Georgi Georgiev \/ Straw? No, too stupid a fad. I put soot on \/ |
| 43 |
/\ chutz@×××.net /\ warts. /\ |
| 44 |
\/ +81(90)6266-1163 \/ \/ |
| 45 |
|
| 46 |
-- |
| 47 |
gentoo-dev@g.o mailing list |
Archives