public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pete Gavin <pete@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] allowing configuration of builds?
Date: Mon Feb  5 16:39:02 2001	[thread overview]
Message-ID: <20010205163815.D13748@cvs.gentoo.org> (raw)
In-Reply-To: <3A7F31EA.D7639196@gottinger.de>; from 320095285153-0001@t-online.de on Tue, Feb 06, 2001 at 12:06:19AM +0100

On Tue, Feb 06, 2001 at 12:06:19AM +0100, Achim Gottinger wrote:
> So it is more definatly a kernel/reiserfs  problem. Things work better with
> 2.4.0-ac11.
> 
> What do you think about that temporary solution for the kernel configuration.
> 
> if [ "${LOPCAL_KERNEL_CONFIG}" == "interactive" ]
> then
>     make menuconfig
> else
>     if [ "${LOCAL_KERNEL_CONFIG}" ]
>     then
>         cp ${LOCAL_KERNEL_CONFIG} .config
>      else
>         cp ${FILESDIR}...../config .config
>      fi
>      yes "" | make oldconfig
> fi
> 
> This way you can eigther pass your own config file or use the interactive
> method.
> If the var is not set it behaves as before.
> 
> achim
> 

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...

I'll email it to you separately from this message.

Pete




  reply	other threads:[~2001-02-05 23:38 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 [this message]
2001-02-05 18:05             ` drobbins

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=20010205163815.D13748@cvs.gentoo.org \
    --to=pete@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