Why don't we separate menuconfig from the kernel?
Hi,
A number of packages (e.g., busybox) use some, more or less broken, version of menuconfig. Would it make sense to move menuconfig to a separate well-defined package?
Nooo? Why not?
Signature · 1 line
Krzysztof Halasa
Hi,
Quoted 9 lines · Krzysztof Halasa
Hi,
A number of packages (e.g., busybox) use some, more or less broken, version of menuconfig. Would it make sense to move menuconfig to a separate well-defined package?
Nooo? Why not?
--
Krzysztof Halasa
menuconfig is _part_ of kernel configuration system.
Regards,
Michal Piotrowski
Quoted 1 line · Michal Piotrowski
menuconfig is _part_ of kernel configuration system.
Sure, dialog is "part" of menuconfig. Your point being?
Signature · 1 line
Krzysztof Halasa
Quoted 6 lines · Krzysztof Halasa
Hi,
A number of packages (e.g., busybox) use some, more or less broken, version of menuconfig. Would it make sense to move menuconfig to a separate well-defined package?
What exactely is it you want to make a sepperate package?
menuconfig is just a little bit of the kbuild system which also includes xconfig, config, gconfig, oldconfig, etc. menuconfig is just a dialog based frontend to the kbuild system which consists of configuration options, help texts, dependency info etc.
menuconfig uses dialog to present its menus and dialog boxes (using ncurses), and if you want to build something else using dialog, then that already exists as a sepperate program that has nothing to do with kbuild. On my system (Slackware) it's installed as /bin/dialog and comes from the pkgtools-10.2.0-i486-5 package.
I don't think it makes much sense to split the parts of kbuild that make up menuconfig out into a standalone thing. kbuild (and thus menuconfig) has little use outside the kernel. The dialog tool is a different matter, but that is already a sepperately developed thing (
http://hightek.org/dialog/ ) .
Signature · 3 lines
Jesper Juhl <[email protected]> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html
Quoted 21 lines · On Sun, 18 Sep 2005 02:46:35 +0200 Jesper Juhl wrote:
Quoted 6 lines · Krzysztof Halasa
Hi,
A number of packages (e.g., busybox) use some, more or less broken, version of menuconfig. Would it make sense to move menuconfig to a separate well-defined package?
What exactely is it you want to make a sepperate package?
menuconfig is just a little bit of the kbuild system which also includes xconfig, config, gconfig, oldconfig, etc. menuconfig is just a dialog based frontend to the kbuild system which consists of configuration options, help texts, dependency info etc.
menuconfig uses
dialogto present its menus and dialog boxes (using ncurses), and if you want to build something else using dialog, then that already exists as a sepperate program that has nothing to do with kbuild. On my system (Slackware) it's installed as/bin/dialogand comes from the pkgtools-10.2.0-i486-5 package.
Quoted 5 lines
I don't think it makes much sense to split the parts of kbuild that make up menuconfig out into a standalone thing. kbuild (and thus menuconfig) has little use outside the kernel. The
dialogtool is a different matter, but that is already a sepperately developed thing (
http://hightek.org/dialog/ ) .
OTOH, Christoph Hellwig used to maintain 'mconf' out-of-tree and it worked decently, so it seems not a big deal to so do.
---
~Randy
You can't do anything without having to do something else first. -- Belefant's Law
Quoted 23 lines · Randy.Dunlap
Quoted 21 lines · On Sun, 18 Sep 2005 02:46:35 +0200 Jesper Juhl wrote:
Quoted 6 lines · Krzysztof Halasa
Hi,
A number of packages (e.g., busybox) use some, more or less broken, version of menuconfig. Would it make sense to move menuconfig to a separate well-defined package?
What exactely is it you want to make a sepperate package?
menuconfig is just a little bit of the kbuild system which also includes xconfig, config, gconfig, oldconfig, etc. menuconfig is just a dialog based frontend to the kbuild system which consists of configuration options, help texts, dependency info etc.
menuconfig uses
dialogto present its menus and dialog boxes (using ncurses), and if you want to build something else using dialog, then that already exists as a sepperate program that has nothing to do with kbuild. On my system (Slackware) it's installed as/bin/dialogand comes from the pkgtools-10.2.0-i486-5 package.
Quoted 9 lines
Quoted 5 lines
I don't think it makes much sense to split the parts of kbuild that make up menuconfig out into a standalone thing. kbuild (and thus menuconfig) has little use outside the kernel. The
dialogtool is a different matter, but that is already a sepperately developed thing (
http://hightek.org/dialog/ ) .OTOH, Christoph Hellwig used to maintain 'mconf' out-of-tree and it worked decently, so it seems not a big deal to so do.
I still fail to see the point of doing so, even if doable.
Signature · 3 lines
Jesper Juhl <[email protected]> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html
Quoted 1 line · Jesper Juhl
What exactely is it you want to make a sepperate package?
Just the menuconfig (mconf) at first. OTOH it might make sense to move them all.
Quoted 4 lines
menuconfig is just a little bit of the kbuild system which also includes xconfig, config, gconfig, oldconfig, etc. menuconfig is just a dialog based frontend to the kbuild system which consists of configuration options, help texts, dependency info etc.
Sure, that's what I mean. It's used for configuring the kernel, but other packages use it (well, some version) too. Example: busybox.
There is no much point in keeping more than one copy. They are completely independent of the kernel, all the kernel wants is to pass them some Kconfig file and expect data in .config. (oldconfig uses .config.old).
There is a question about config language and possible future changes. Not a serious problem IMHO.
Quoted 3 lines
I don't think it makes much sense to split the parts of kbuild that make up menuconfig out into a standalone thing. kbuild (and thus menuconfig) has little use outside the kernel.
It's not exactly the case.
Signature · 1 line
Krzysztof Halasa
Quoted 7 lines · Krzysztof Halasa
Quoted 1 line · Jesper Juhl
What exactely is it you want to make a sepperate package?
Just the menuconfig (mconf) at first. OTOH it might make sense to move them all.
And if you do that, then you'd be shipping a kernel source that it would be impossible for users to configure without installing sepperate tools - and tools (unlike for example gcc) that very few people would have a need for outside configuring their kernel. Not a good idea in my oppinion.
Quoted 10 lines
Quoted 4 lines
menuconfig is just a little bit of the kbuild system which also includes xconfig, config, gconfig, oldconfig, etc. menuconfig is just a dialog based frontend to the kbuild system which consists of configuration options, help texts, dependency info etc.
Sure, that's what I mean. It's used for configuring the kernel, but other packages use it (well, some version) too. Example: busybox.
There is no much point in keeping more than one copy. They are completely independent of the kernel, all the kernel wants is to pass
I think there's a point; the kernel source should contain its own configuration tools.
Just think of how many users would complain that "the kernel is broken, I can't configure it" and similar. Also, what would ensure that the config/build tools would always stay in sync with other kernel changes? Right now things stay in sync since everyone are using the same version of the tools that ship with any given kernel and if something breaks it's fixed up along with everything else. Move it out of the kernel tree and you'll end up having users trying to use old tools to build a new kernel (or new tools to build an old kernel) and there's bound to be breakage at some point - why have those extra problems?
Quoted 3 lines
them some
Kconfigfile and expect data in .config. (oldconfig uses .config.old).
if you extract a fresh kernel source and copy your old .config to .config in the new kernel source dir, then "make oldconfig" will read that .config and write a new one as well...
Quoted 3 lines
There is a question about config language and possible future changes. Not a serious problem IMHO.
I disagree.
Quoted 5 lines
Quoted 3 lines
I don't think it makes much sense to split the parts of kbuild that make up menuconfig out into a standalone thing. kbuild (and thus menuconfig) has little use outside the kernel.
It's not exactly the case.
If someone wants to use the tools outside the kernel, then let them fork off a version and maintain that out-of tree. The in-kernel and out-of-kernel could borrow code and fixes from eachother if needed/wanted, but I personally believe there needs to be a version shipping as part of the source tree.
Signature · 3 lines
Jesper Juhl <[email protected]> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html
Quoted 4 lines · Jesper Juhl
And if you do that, then you'd be shipping a kernel source that it would be impossible for users to configure without installing sepperate tools - and tools (unlike for example gcc) that very few people would have a need for outside configuring their kernel.
So what? We already have tools which are needed for just one thing. This one is at least for configuring more than one program.
Of course, the kernel (kbuild or running the kernel) requires many things, isn't it the UNIX philosophy?
Remember ksymoops? _That_ was a single purpose.
Quoted 2 lines
I think there's a point; the kernel source should contain its own configuration tools.
Why only them? Why not the compiler toolchain (encoded with sharutils) and some shell so you can bootstrap it over serial console? :-)
Quoted 2 lines
Just think of how many users would complain that "the kernel is broken, I can't configure it" and similar.
Such users use distribution kernels. Distributions have package dependencies which can install anything needed automatically.
How many times have you seen people complaining that the kernel is broken as one "can't compile it" (due to missing binutils or even gcc)?
Quoted 3 lines
Also, what would ensure
that the config/build tools would always stay in sync with other kernel changes?
People sending patches, of course, and the maintainer doing kernel work as well. What ensures that, say, udev stays in sync? And udev is new and changing.
Quoted 3 lines
if you extract a fresh kernel source and copy your old .config to .config in the new kernel source dir, then "make oldconfig" will read that .config and write a new one as well...
Sure, I don't know why I mentioned .config.old, they all use it the same. Writing at 3 am, possibly.
Quoted 4 lines
If someone wants to use the tools outside the kernel, then let them fork off a version and maintain that out-of tree. The in-kernel and out-of-kernel could borrow code and fixes from eachother if needed/wanted,
That's what is currently done, but it doesn't seem so smart from maintenance POV. And UNIX philosophy, you know.
Signature · 1 line
Krzysztof Halasa
Quoted 9 lines · Jesper Juhl
Quoted 7 lines · Krzysztof Halasa
Quoted 1 line · Jesper Juhl
What exactely is it you want to make a sepperate package?
Just the menuconfig (mconf) at first. OTOH it might make sense to move them all.
Quoted 5 lines
And if you do that, then you'd be shipping a kernel source that it would be impossible for users to configure without installing sepperate tools - and tools (unlike for example gcc) that very few people would have a need for outside configuring their kernel. Not a good idea in my oppinion.
There are, in my opinion, two issues: where is kconfig maintained, and is it shipped with the kernel. I think each kernel tarball should contain the version of kconfig it expects to be configured with, because there isn't a commitment to having kconfig be compatible between versions. On the other hand, I don't see any reason that it has to be maintained in the kernel's git repositories.
Git actually supports this. Sam could have a repository with only the kbuild files, and people could pull it normally, and it would all work trivially (so long as people didn't try to modify kbuild by sending patches to Linus). The only tricky thing is that this repository can't have the linux-with-kbuild repository as an ancestor, because then it would remove stuff; so, if people want kbuild history, it would need to be recreated separately.
The advantage would be that people who wanted the latest version of kbuild could always get it without the kernel; the disadvantage is that kernel developers who want to change kbuild would have to remember not to send this changes into the kernel tree. I don't know if it would be more or less convenient for Sam not to have the rest of the kernel tree around kbuild.
-Daniel
*This .sig left intentionally blank*
Quoted 7 lines · Krzysztof Halasa
Quoted 4 lines
menuconfig is just a little bit of the kbuild system which also includes xconfig, config, gconfig, oldconfig, etc. menuconfig is just a dialog based frontend to the kbuild system which consists of configuration options, help texts, dependency info etc.
Sure, that's what I mean. It's used for configuring the kernel, but other packages use it (well, some version) too. Example: busybox.
One of Linux's main problems is that all daemons that drive kernel core functionality are cluttered over various separate projects. While this allows for independent development, it's annoying if you need to hunt down the various daemons (udev, autofs, hotplug, iproute, to name the first that come to mind) only to find out the new version doesn't suit your distro. I'd rather wish there was a standard kernel "daemons" package.
Quoted 1 line
There is no much point in keeping more than one copy. They are
Why should other projects that recycle kernel code impact how the kernel itself is made.
Signature · 1 line
Matthias Andree
Quoted 7 lines · Matthias Andree
One of Linux's main problems is that all daemons that drive kernel core functionality are cluttered over various separate projects. While this allows for independent development, it's annoying if you need to hunt down the various daemons (udev, autofs, hotplug, iproute, to name the first that come to mind) only to find out the new version doesn't suit your distro. I'd rather wish there was a standard kernel "daemons" package.
Who would select what is a standard kernel daemon and what is not? Who would maintain the package?
Quoted 2 lines
Why should other projects that recycle kernel code impact how the kernel itself is made.
It's NOT kernel code.
Signature · 1 line
Krzysztof Halasa