From: Georgi Georgiev <chutz@gg3.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] xorg-x11-6.8.0-r4 to go ~arch --- ~sparc tests good.
Date: Wed, 8 Dec 2004 09:16:17 +0900 [thread overview]
Message-ID: <20041208001616.GA21299@lion.gg3.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0412072331460.30420@terciopelo.krait.us>
maillog: 07/12/2004-23:36:49(+0000): Ferris McCormick types
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wed, 8 Dec 2004, Georgi Georgiev wrote:
>
> >maillog: 08/12/2004-07:52:19(+0900): Georgi Georgiev types
> >>maillog: 07/12/2004-19:59:05(+0000): Ferris McCormick types
> >>>6. NOTE: The two 'is_kernel' tests produce error messages, but (for me,
> >>> at any rate) ebuild operation is correct anyway. I have not
> >>> investigated further, but as I recall, the messages were:
> >>> [: wrong number of arguments (for the check kernel-2.2.x)
> >>> Command '*' not understood
> >>
> >>This is what I had in my overlay while testing the ebuild yesterday.
> >>The linux-info.eclass kernel_is() should only return an exit code so its
> >>output should not be looked at. I.e. those "[" and "$(" are not needed.
> >
> >Ah, well, linux-info broke in the meantime, that's all.
> >
>
> Thanks for the information. For your confusion, there is a 'kernel_is'
> in linux-info.eclass, and an 'is_kernel' in x11.eclass. The ebuilds
> used to use is_kernel; now they use kernel_is, and perhaps the
> difficulties started with that?
is_kernel will probably dissapear soon enough.
And to the attention of spyderous: kernel_is from linux-info returns a
valid exit code and outputs lots of einfos, therefore the [ $(kernel_is
..) ] and the other $(kernel_is) must not be in a subshell whose output
is passed to the command line (hence the "Command '*' not understood").
And lastly, well, sorry for the misinformation. linux-info did indeed
break, but only for me I guess (am I the only one using KERNEL_OUTPUT,
because nobody else seems to complain when stuff related to
KERNEL_OUTPUT is obviously broken), which was unrelated to the current
problem. It's just that when I tried it, there were two problems to
solve.
--
\/ Georgi Georgiev \/ Straw? No, too stupid a fad. I put soot on \/
/\ chutz@gg3.net /\ warts. /\
\/ +81(90)6266-1163 \/ \/
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-12-08 0:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 10:48 [gentoo-dev] xorg-x11-6.8.0-r4 to go ~arch Donnie Berkholz
2004-12-06 15:42 ` Georgi Georgiev
2004-12-06 18:17 ` Donnie Berkholz
2004-12-06 18:54 ` Hans-Werner Hilse
2004-12-06 21:37 ` Georgi Georgiev
2004-12-06 22:06 ` Georgi Georgiev
2004-12-06 22:17 ` Georgi Georgiev
2004-12-06 23:10 ` Donnie Berkholz
2004-12-07 0:38 ` Donnie Berkholz
2004-12-07 1:01 ` Georgi Georgiev
2004-12-07 3:01 ` Donnie Berkholz
2004-12-07 2:17 ` Donnie Berkholz
2004-12-07 1:27 ` Georgi Georgiev
2004-12-07 1:37 ` [gentoo-dev] HOSTCONF in global scope Georgi Georgiev
2004-12-07 1:52 ` [gentoo-dev] Double stripping in strip_execs() Georgi Georgiev
2004-12-07 12:34 ` [gentoo-dev] xorg-x11-6.8.0-r4 to go ~arch -- ~sparc OK Ferris McCormick
2004-12-07 19:59 ` [gentoo-dev] xorg-x11-6.8.0-r4 to go ~arch --- ~sparc tests good Ferris McCormick
2004-12-07 22:52 ` Georgi Georgiev
2004-12-07 23:02 ` Georgi Georgiev
2004-12-07 23:36 ` Ferris McCormick
2004-12-08 0:16 ` Georgi Georgiev [this message]
2004-12-08 0:38 ` Donnie Berkholz
2004-12-08 2:19 ` Georgi Georgiev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041208001616.GA21299@lion.gg3.net \
--to=chutz@gg3.net \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox