From: <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] allowing configuration of builds?
Date: Mon Feb 5 18:05:02 2001 [thread overview]
Message-ID: <20010205180423.E14106@cvs.gentoo.org> (raw)
In-Reply-To: <20010205163815.D13748@cvs.gentoo.org>; from pete@gentoo.org on Mon, Feb 05, 2001 at 04:38:15PM -0700
On Mon, Feb 05, 2001 at 04:38:15PM -0700, Pete Gavin wrote:
> Well, I've done a simple addition to the current ebuild script that will
> set INTERACTIVE=y in the .ebuild file if it is passed w/ the -i switch.
> I put it in sys-apps/portage/files/ebuild-pete. I'll also attach a
> linux kernel ebuild script I put together to take advantage of this...
OK; continue making your changes to ebuild-pete. I'll need to think more
about the best way to handle an interactive compile process.
The way I upgrade to a new kernel is to first merge linux-sources. Then
I cd to /usr/src/linux and make menuconfig and compile and install the
kernel by hand. So for linux-sources, an interactive merge isn't needed.
The "linux" ebuild contains the default pre-compiled kernel for Gentoo Linux.
This kernel should be pre-configured by us to support the widest variety of
hardware configurations possible. You shouldn't need an interactive compile
mode for this kernel.
I think we avoid this whole interactive compile problem if people who compile
their own kernels simply use linux-sources instead. Which reminds me, I need
to fix the install guide again :) I forgot to mention that the linux-sources
need to be merged first.
--
Daniel Robbins <drobbins@gentoo.org>
President/CEO http://www.gentoo.org
Gentoo Technologies, Inc.
prev parent reply other threads:[~2001-02-06 1:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-05 14:43 [gentoo-dev] allowing configuration of builds? Pete Gavin
2001-02-05 15:07 ` Pete Gavin
2001-02-05 15:31 ` Achim Gottinger
2001-02-05 15:37 ` Pete Gavin
2001-02-05 15:49 ` Achim Gottinger
2001-02-05 16:02 ` Pete Gavin
2001-02-05 16:33 ` Achim Gottinger
2001-02-05 16:39 ` Pete Gavin
2001-02-05 18:05 ` drobbins [this message]
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=20010205180423.E14106@cvs.gentoo.org \
--to=drobbins@gentoo.org \
--cc=gentoo-dev@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