public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W. Trevor King" <wking@tremily.us>
To: Catalyst <gentoo-catalyst@lists.gentoo.org>
Cc: "W. Trevor King" <wking@tremily.us>
Subject: [gentoo-catalyst] [PATCH 0/6] Make external kernel configs optional
Date: Sat, 09 Feb 2013 15:45:32 -0500	[thread overview]
Message-ID: <cover.1360442556.git.wking@tremily.us> (raw)
In-Reply-To: <CA+_+8cpJECEsEcozyBtLF179CFPXOYkLztfzA4SE3rBPifmT7Q@mail.gmail.com>

From: "W. Trevor King" <wking@tremily.us>

On Sat, Feb 09, 2013 at 04:56:43AM -0800, Chris White wrote:
> > What's changed?  Why do I need to seed catalyst with a config file,
> > when I don't need to from the handbook instructions?  Maybe this usage
> > is just unimplemented because nobody has needed it yet?
> > …
>
> It's a TODO[1] right now. Personally though I recommend setting up a config
> manually, as it's a lot easier to debug kernel setup related issues when
> you're the one who configured everything and not genkernel.

Now it's done ;).  I tested it today, and genkernel (unsurprisingly),
built its kernel fine without a seed config.

W. Trevor King (6):
  generic_stage_target: Split ._build_kernel() out of .build_kernel()
  generic_stage_target: Split ._copy_kernel_config() from
    ._build_kernel()
  generic_stage_target.py: Dedent the bulk of ._build_kernel()
  generic_stage_target: Split ._copy_initramfs_overlay() from
    ._build_kernel()
  generic_stage_target: Handle unspecified boot/kernel/<kname>/config
  kmerge.sh: Make /var/tmp/${clst_kname}.config optional

 modules/generic_stage_target.py | 198 ++++++++++++++++++++--------------------
 targets/support/kmerge.sh       |  21 +++--
 2 files changed, 114 insertions(+), 105 deletions(-)

-- 
1.8.1.336.g94702dd



  parent reply	other threads:[~2013-02-09 20:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-09 12:15 [gentoo-catalyst] stage4 kernel config for genkernel? W. Trevor King
2013-02-09 12:56 ` Chris White
2013-02-09 13:18   ` W. Trevor King
2013-02-09 20:45   ` W. Trevor King [this message]
2013-02-09 20:45     ` [gentoo-catalyst] [PATCH 1/6] generic_stage_target: Split ._build_kernel() out of .build_kernel() W. Trevor King
2013-02-09 20:45     ` [gentoo-catalyst] [PATCH 2/6] generic_stage_target: Split ._copy_kernel_config() from ._build_kernel() W. Trevor King
2013-02-09 20:45     ` [gentoo-catalyst] [PATCH 3/6] generic_stage_target.py: Dedent the bulk of ._build_kernel() W. Trevor King
2013-02-09 20:45     ` [gentoo-catalyst] [PATCH 4/6] generic_stage_target: Split ._copy_initramfs_overlay() from ._build_kernel() W. Trevor King
2013-02-09 20:45     ` [gentoo-catalyst] [PATCH 5/6] generic_stage_target: Handle unspecified boot/kernel/<kname>/config W. Trevor King
2013-02-09 20:45     ` [gentoo-catalyst] [PATCH 6/6] kmerge.sh: Make /var/tmp/${clst_kname}.config optional W. Trevor King
2013-03-01  5:57       ` [gentoo-catalyst] [PATCH] kmerge.sh: Fix line wrapping typo from 9ceebbf W. Trevor King
2013-03-01  6:06         ` Matt Turner

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=cover.1360442556.git.wking@tremily.us \
    --to=wking@tremily.us \
    --cc=gentoo-catalyst@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