Every distro has to package the kernel tree using their own unique package
files. Some parts of the process are built-in to the kernel source and are
easy: build, install, and headers. Some parts are not: configs, devel
package, userspace tools package, tests, distro versioning, changelogs,
custom patches, etc.
This discussion revolves around some of the issues and difficulties a
distro maintainer faces when packaging the kernel source code. What changes
can we agree to push upstream to make our lives easier.
Further, discuss possibilities of plugging in distro packaging into the
kernel source tree (through external means or internal hooks). This allows
developers to quickly build (from a common devel env) a particular
distro-like kernel for proper testing.
Sample topics include:
* config maintainence for distros
* top-level Makefile hooks for distros
* make devel_install -like command
* distro versioning
|I agree to abide by the anti-harassment policy||Yes|