[Savannah-hackers] savannah.gnu.org: submission of kernkit

[dougporter]

A package was submitted to savannah.gnu.org.
This mail was sent to address@hidden, address@hidden


Doug Porter <address@hidden> described the package as follows:
License: gpl
Other License: 
Package: kernkit
System name: kernkit
This package does NOT want to apply for inclusion in the GNU project

This is a resubmission after sending the tarball to address@hidden, as 
requested by Loic.

>From the README:


   kernkit 0.5
   Copyright (c) 2002 Doug Porter address@hidden
   GPL license.
   
   Kernkit is a collection of small command line utilities to handle the
   tedious and error prone parts of playing with the Linux kernel source
   code. Kernkit goes from applying version patches to setting up /boot
   and /lib/modules. It patches, configures, makes, installs, and
   customizes. You can find the instructions on how to do all this by
   hand if you search through various system documents, but kernkit is
   much easier.
   
   Requirements
   
     Perl
   
     Linux kernel source 

   Installation
   
     1) Set the \"#!/usr/bin/perl\" at the top of each file to match the
     location of perl on your system.
     2) Copy the utilities to a directory in your path, such as
     /usr/local/sbin.
     3) If your Linux kernel source isn\'t in /usr/src make a link from
     /usr/src/linux-X.Y.Z. \"X.Y.Z\" means the kernel version, such as
     \"2.4.6\".
     
   Quick start
   
     kernpatch <patch dir>
     kernconfig <new version>
     
   kernpatch
   
     Creates a copy of the kernel source directory and consecutively
     applies all the version patches you have. Checks gpg signature on
     any patch that has a coresponding signature file. The new source
     directory is ready for \'kernconfig <version>\'.
     
     Don\'t untar or un-bzip the patch files.
     
     If you have signature files for the patches but don\'t have gpg
     installed kernpatch will warn you. If you don\'t want to see these
     warnings, don\'t put the signature files in the patch directory.
     
     If you don\'t have a \"trust path\" to the key used to sign the
     patches, gpg will give you several warnings. That\'s because without
     a trust path you may know the patch was signed, but you don\'t know
     who really signed it. See the gpg docs for more on trust paths.
     
     usage: kernpatch <patch dir> [<source dir>]
     
            <patch dir>   Contains the patch-X.Y.Z.* files to apply.
            <source dir>  Defaults to /usr/src. Must contain at least one 
linux-X.Y.Z source
                          code subdirectory. The new source subdirectory will 
be created
                          here.
     
   kernconfig
   
     Configures and installs a kernel from source. Handles details from
     \"make xconfig\" through make, installation, and customization.
     Invokes other kernkit utilities as needed. If you\'re not running
     Xwindows, replace \'xconfig\' with \'menuconfig\' or \'config\'.
     
     It\'s a good idea to check your configuration whenever you rebuild
     your kernel, but if you just quit xconfig, kernconfig will continue
     to build and install your kernel.
     
     usage: kernconfig [<version>]
     
   kernmake
   
     Make clean, dep, bzImage, modules, and modules_install.
     
     usage: kernmake [<version>]
     
   kerninstall
   
     Installs kernel into /boot/bzImage. Configures /boot, system map,
     and /lib/modules. Runs lilo. Links /usr/src/linux.
     
     Before running kerninstall, be sure to
     
     1) run kernconfig or kernmake
     2) have a boot in /etc/lilo.conf with an image of /boot/bzImage
     
     Some kernels and some kernel configurations don\'t work. Keep a
     working kernel around. It\'s always a very good idea to have a boot
     in /etc/lilo.conf that uses a known working kernel. The System.map
     will be wrong for your emergency backup kernel, but it will usually
     run well enough for you to fix things. A boot floppy is also handy.
     
     usage: kerninstall [<version>]
     
   kerncustom
   
     Put your local customization here. If you don\'t need any
     customization just remove kerncustom.
     
     The example provided makes and installs some modules that aren\'t in
     the standard kernel. It\'s almost certainly not what you want, but
     should be harmless.
     
     If you\'re customizing a kernel version that\'s not running, you may
     need to reboot under the new version, rerun kerncustom, and reboot
     again.
     
     usage: kerncustom [<version>]

----------------------------------
Works, but v0.5 and no web site, so \"I\'m working on it\".

This is a resubmission after sending the tarball to address@hidden, as 
requested by Loic.