From: Stefan Schweizer <sschweizer@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] kernel-mod.eclass deprecation and effected ebuilds
Date: Mon, 25 Apr 2005 18:06:04 +0200 [thread overview]
Message-ID: <e79639220504250906db82ea6@mail.gmail.com> (raw)
In-Reply-To: <200504251150.18698.vapier@gentoo.org>
Most of the current linux-mod-ebuilds do not build with portage-cvs
because KV_DIR is not available in global scope any more.
portage-cvs does not repeatedly source the ebuild after every stage
and is more sane in this case.
What is needed to fix the problems:
BUILD_PARAMS="--with-kernel=${KV_DIR}
...
should be changed to:
pkg_setup() {
linux-mod_pkg_setup
BUILD_PARAMS="--with-kernel=${KV_DIR}
}
Now it works with every portage-version and only requires a variable
to be set when it is actually set.
Regards,
Stefan
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-25 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 14:51 [gentoo-dev] kernel-mod.eclass deprecation and effected ebuilds John Mylchreest
2005-04-25 15:19 ` Ned Ludd
2005-04-25 15:29 ` Chris Gianelloni
2005-04-25 15:50 ` Mike Frysinger
2005-04-25 16:06 ` Stefan Schweizer [this message]
2005-04-27 17:25 ` Alastair Tse
2005-04-28 12:26 ` Henrik Brix Andersen
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=e79639220504250906db82ea6@mail.gmail.com \
--to=sschweizer@gmail.com \
--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