Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #64640

Re: Question about Workflow for kernel packaging

From Ben Hutchings <ben@decadent.org.uk>
Newsgroups linux.debian.kernel
Subject Re: Question about Workflow for kernel packaging
Date 2019-08-05 18:30 +0200
Message-ID <yrO1X-7b2-1@gated-at.bofh.it> (permalink)
References <yrNfA-6EK-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Mon, 2019-08-05 at 11:22 -0400, thomasw@fastmail.cn wrote:
> Hi,
> I am trying to understand the workflow that people use to work on the
> kernel. What is the best way to run make menuconfig or make oldconfig
> based on the kconfig created by rules.gen when you update the kernel?
> Also, when you change values, how do you ensure that they are written
> to the correct file whether it be the main config, the kernelarch
> etc? Thanks.

There is no way to convert .config back into multiple partial config
files, so we don't use commands like "make menuconfig" to update
debian/config.

Instead, we have to start by deciding which architectures or flavours a
change should apply to, and based on that we will update the
appropriate file.  We can verify that the change is actually effective
by running "debian/rules setup" or similar and examining the generated
full config files.

debian/README.source has more information about the partial config
files.

Ben.

-- 
Ben Hutchings
Beware of programmers who carry screwdrivers. - Leonard Brandwein


Back to linux.debian.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Question about Workflow for kernel packaging thomasw@fastmail.cn - 2019-08-05 17:40 +0200
  Re: Question about Workflow for kernel packaging Ben Hutchings <ben@decadent.org.uk> - 2019-08-05 18:30 +0200
    Re: Question about Workflow for kernel packaging thomasw@fastmail.cn - 2019-08-06 06:50 +0200

csiph-web