Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #64639 > unrolled thread
| Started by | thomasw@fastmail.cn |
|---|---|
| First post | 2019-08-05 17:40 +0200 |
| Last post | 2019-08-06 06:50 +0200 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.kernel
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
| From | thomasw@fastmail.cn |
|---|---|
| Date | 2019-08-05 17:40 +0200 |
| Subject | Question about Workflow for kernel packaging |
| Message-ID | <yrNfA-6EK-7@gated-at.bofh.it> |
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.
[toc] | [next] | [standalone]
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2019-08-05 18:30 +0200 |
| Message-ID | <yrO1X-7b2-1@gated-at.bofh.it> |
| In reply to | #64639 |
[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
[toc] | [prev] | [next] | [standalone]
| From | thomasw@fastmail.cn |
|---|---|
| Date | 2019-08-06 06:50 +0200 |
| Message-ID | <yrZA5-62p-1@gated-at.bofh.it> |
| In reply to | #64640 |
On Mon, Aug 5, 2019, at 12:22 PM, Ben Hutchings wrote: > debian/README.source has more information about the partial config > files. Thanks for all this information and taking the time to respond to my mail. It really got me going on the right track. I am still learning Debian packaging but I think everything is starting to fall into place as far as things go with understanding how the kernel build process works. I read through the rules file, the gencontrol python stuff, and the kconfigeditor2 in the kernel-team package so far to get a handle on how all these things work. I am really impressed with all the tooling you folks have in place.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web