From: Peter Johanson <latexer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] FYI: koutput/config-kernel should *NOT* be used/supported currently.
Date: Wed, 29 Sep 2004 19:26:20 -0700 [thread overview]
Message-ID: <20040930022619.GB28747@butchy.cubesearch.com> (raw)
Hey all,
Been busy with lots of other things, and dreading sending this anyway,
but I wanted to clear things up Re: the koutput/kbuild stuff that I'd
worked on to fix some problems previously related to 2.6 kernel build
issues.
Unfortunately, the fix that was 95% implemented, and had the beginnings
of code in the tree got ham-strung by a combination of kernel stuff
changing under my/our feet, and Real Life (tm) things coming in at just
the wrong time.
As a result, the kmod.eclass, and config-kernel have several problems,
and are only 1/2 implemented anyway. Sooo, don't use kmod.eclass. Just
don't. config-kernel i will be package.masking as well soon. I know
there are a few ebuilds out there that currently use kmod.eclass for a
few things. I'll be contacting those maintainers over the next few days
to address things with them, and get them sorted out with how to get
things working with 2.6.6 and newer kernels. If you get any bugs from
people complaining about such and such ebuild not working with koutput,
assing or CC me, and i'll deal with it. Thanks.
Sorry for any confusion folks.
-pete
--
Peter Johanson
<latexer@gentoo.org>
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2004-09-30 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 2:26 Peter Johanson [this message]
2004-10-02 14:40 ` [gentoo-dev] FYI: koutput/config-kernel should *NOT* be used/supported currently Daniel Drake
2004-10-02 14:09 ` Peter Johanson
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=20040930022619.GB28747@butchy.cubesearch.com \
--to=latexer@gentoo.org \
--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