Make a customized Linux package NAME derived from the LINUX package.

If NAME is not given, then it defaults to the same name as the LINUX package.

Unless SOURCE is given the source of LINUX is used.

A DEFCONFIG file to be used can be given as an origin, as a file-like object (file-append, local-file etc.), or as a string with the name of a defconfig file available in the Linux sources. If DEFCONFIG is not given, then a defconfig file will be saved from the LINUX package configuration.

MODCONFIG is an origin or file-like object used for make localmodconfig to disable unlisted modules. For instance, this can come from using modprobed-db periodically on a running machine to find all loaded modules.

Additional CONFIGS will be used to modify the given or saved defconfig, which will finally be used to build Linux.

CONFIGS can be a list of strings, with one configuration per line. The usual defconfig syntax has to be used, but there is a special extension to ease the removal of configurations. Comment lines are supported as well.

Here is an example:

'(;; This string defines the version tail in 'uname -r'. "CONFIG_LOCALVERSION=\"-handcrafted\" ;; This '# CONFIG_... is not set' syntax has to match exactly! "# CONFIG_BOOT_CONFIG is not set" "CONFIG_NFS_SWAP=y" ;; This is a multiline configuration: "CONFIG_E1000=y # This is a comment, below follows an extension to unset a configuration: CONFIG_CMDLINE_EXTEND")

A string of configurations instead of a list of configuration strings is also possible.

EXTRA-VERSION can be a string overwriting the EXTRAVERSION setting of the LINUX package, after being prepended by a hyphen. It will be visible in the output of 'uname -r' behind the Linux version numbers.