1. 15 Feb, 2016 1 commit
    • Manoj Srivastava's avatar
      Root cause failure to build debs · 9b1770e4
      Manoj Srivastava authored
      Firstly, this is not true in general, and I could not reproduce it as
      long as I use fakeroot.
      Bug fix: "cannot produce debs anymore", thanks to Ritesh Raj Sarraf
      The real issue here was that the kernel was built using the deprecated
      sudo, instead of fakeroot, and created ./debian directory as
      root. Clean, however, is not run as root, so it could not delete
      ./debian, and failed. This is now documented. (Closes: #812470).
      Signed-off-by: Manoj Srivastava's avatarManoj Srivastava <srivasta@debian.org>
  2. 10 Jan, 2016 1 commit
  3. 18 Nov, 2015 1 commit
    • Ying-Chun Liu's avatar
      · 709ac7e0
      Ying-Chun Liu authored
      kernel-package (13.014+nmu3) unstable; urgency=low
        * Non-maintainer upload.
        * Fix the install device-tree rule by dtbs_install (Closes: #804518)
        * Include patches to support s390x (Closes: #751928)
      # imported from the archive
  4. 06 Oct, 2015 1 commit
    • Ying-Chun Liu's avatar
      · 57a013d0
      Ying-Chun Liu authored
      kernel-package (13.014+nmu2) unstable; urgency=low
        * Non-maintainer upload.
        * Install device-tree dtbs. (Closes: #782759)
        * Support arm64 arch. (Closes: #796064, #796879, #799968)
      # imported from the archive
  5. 12 May, 2014 1 commit
    • Manoj Srivastava's avatar
      [master]: New bugfixing release. · 0cbba845
      Manoj Srivastava authored
      * The underlying kernel tree has long removed support for zImage
        images. This makes bzImage the default, so there is no need to have
        the user specify one or the other, so removed the --zImage and the
        --bzImage options from kernel-package. Removing this also removed code
        that caused confusion in the image names when --bzImage argment was
        used.  (Closes: #574957).
      * Modified the manual pages to reflect the changes aboue. Updated the
        po4a .po files and .pot files.  Also clarified the requirements for
        running as root,, and emphasized that fakeroot is th way to go, and
        running as root is not recommended. Clarified that make-kpkg is
        supposed to be run after configuring the kernel. (Closes: #704116).
      * Previously, the Debian revision had to contain a digit. Now dpkg
        complains if it does not start with a digit. Updated the  sanity
        checks to test for this new constraint.   (Closes: #674101).
      * Removed a versioned dependency on make, for a version older than the
        one present in oldstable.
      Signed-off-by: 's avatarManoj Srivastava <srivasta@golden-gryphon.com>
  6. 08 May, 2014 2 commits
  7. 18 Jul, 2010 1 commit
  8. 15 Feb, 2010 2 commits
  9. 12 Aug, 2009 1 commit
  10. 02 Jun, 2009 1 commit
  11. 13 Apr, 2009 1 commit
    • Manoj Srivastava's avatar
      Added a new feature: overlay directory · 9fe01839
      Manoj Srivastava authored
      This commits add an overlay feature. The specified directory should
      contain files that will be placed in the ./debian directory of the kernel
      sources, in preparation to building the debian packages. The files will
      replace anything in /usr/share/kernel-package that would normally be
      placed there, and it is up to the user to make sure that the files in the
      overlay directory are compatible with make-kpkg.  If you break make-kpkg
      with an overlay file, you get to keep the pieces. The same effect can be
      achieved by setting the environment variable KPKG_OVERLAY_DIR.
      Please  note  that  overlay-dir/Control  and  overlay-dir/changelog are
      special, and variable substitution is performed on these files. Use
      /usr/share/kernel-package/Control and /usr/share/kernel-package/changelog
      files as templates.
      If a overlay-dir/post-install executable (or executable script) exists,
      it shall be run immediately after ./debian is populated.  The  script
      shall be executed in the ./debian directory. This can be used, For
      instance, to delete files the user does not want, or to take actions
      other than simple replacement.
      Signed-Off-By: Manoj Srivastava's avatarManoj Srivastava <srivasta@debian.org>
  12. 09 Apr, 2009 1 commit
    • Manoj Srivastava's avatar
      Add a "debuginfo" package · c24657f1
      Manoj Srivastava authored
      This commit adds support for creating a kernel package which contains
      the Linux kernel debug image. This means the debugging information for
      the modules in the kernel  image package, and the uncompressed vmlinux
      image. This builds on suggestions and code from Troy Heber, Theodore
      Y. Ts'o, and Dann Frazier.
      As support for kexec/kdump support becomes more real, it will be very
      useful to be able to build kernels that have debugging information
      available, but not necessarily to install the debugging information on
      every single client system.
      The .ko object files are stripped of the debugging information before
      they are placed in the standard linux-image installation package.
      However, before that, a copy of the vmlinux and unstripped .ko files
      are saved in a "debuginfo" package.  This means that if someone ends
      up with a crash dump, they can send it to a support engineer and only
      the support engineer needs to install the debuginfo package and use
      the "crash" utility to debug the crash dump.  It's also useful for
      developers, since the debuginfo information can be stored somewhere
      outside of /lib for storing its debug information, for example.  This
      is useful for keeping the size of the root partition small, for those
      who keep / separate from /usr.
      The locations used are compatible also with SystemTap, which provides
      free software infrastructure to simplify the gathering of information
      about the running Linux system. This assists diagnosis of a
      performance or functional problem. SystemTap eliminates the need for
      the developer to go through the tedious and disruptive instrument,
      recompile, install, and reboot sequence that may be otherwise required
      to collect data.
      Closes: #365349, #517290, #373639
      Signed-off-by: Manoj Srivastava's avatarManoj Srivastava <srivasta@debian.org>
  13. 07 Apr, 2009 1 commit
    • Manoj Srivastava's avatar
      make-kpkg removes and re-creates ./debian on every invocation · ecb2bd30
      Manoj Srivastava authored
      This does make the kernel-package far more nimble; we now offer less
      surprise to users who did not expect stampts that the kernel-packagge
      used to not do duplicate work. Now, if you edit a couple of files in the
      kernel source, and run make-kpkg, the kernel will build as
      expected. There are no more "version mismatch" errors, and the kernel
      version can be modified using localconfig as one desires. With this,
      kernel-package can rountinely be used to build kernels out of the git
      The con is that we no longer cater to official kernels, or to anyone who
      expected content in ./debian to persist. At some point, there are plans
      to implement an overlay directory that will shadow
      /usr/share/kernel-package/ruleset, but that is not yet implemented.
      Signed-Off-By: Manoj Srivastava's avatarManoj Srivastava <srivasta@debian.org>
  14. 06 Apr, 2009 1 commit
  15. 02 Apr, 2009 1 commit
    • Manoj Srivastava's avatar
      The postinst no longer manipulates symlinks · f8bc5530
      Manoj Srivastava authored
      This is a shift from previous behaviour. Any symbolic link manipulation
      must now be done with hook scripts in /etc/kernel/*.d directories.
      Firstly, modern boot loaders scan the boot directory for kernel images,
      and the user no longer has to code in the path to the symbolic links that
      the kernel image package used to manipulate.
      Secondly, hardcoding the behaviour into the postinst made for a very
      rigid policy; and user wanted more flexibility than that. There is an
      example shipped with the package that shows a more flexible scheme that
      kept two symbolic links for version 2.4 kernels, and two symbolic links
      for 2.6 kernels; it can be easily modified to keep two links for 2.9
      krenels and two links for 2.8 kernels, or one of each, or whatever the
      user wants.
      Signed-Off-By: Manoj Srivastava's avatarManoj Srivastava <srivasta@debian.org>
  16. 01 Apr, 2009 1 commit
    • Manoj Srivastava's avatar
      Image postinst no longer runs a boot loader · cdcd4782
      Manoj Srivastava authored
      Now that we have a mechanism for running arbitrary scripts when the
      image packages are manipulated, we can stop embedding the boot loader
      actions in the package itself.  This means that lilo, elilo, etc will
      no longer be run directly by the post isnt, and all the code related
      to detecting the boot loader, managing the configuration, and adding
      bits about bootloader documentation is all removed from the postinst.
      This allows the image package to be more flexible, since the end user
      is no longer restricted to the actions encoded in the image
      package. This is a fairly large change.
      Signed-off-by: Manoj Srivastava's avatarManoj Srivastava <srivasta@debian.org>
  17. 17 Feb, 2009 2 commits
    • Manoj Srivastava's avatar
      Remove special case code for official kernels · ce61f777
      Manoj Srivastava authored
      For the longest tine (well,  ever since Herbert Xu too over building
      kernel images from me), kernel-package has carried specal case code for
      official images. This has caused some problems, recently, since the need
      to preserve ./debian has caused no end of problems when the version
      changed out from under ./debian, or when people wanted to edit a file and
      expected kernel-package to do a minimal recompile.
      However, sometime in the Etch release cycle, the kernel team deprecated
      kernel-package as the means of building official kernels, and therefore,
      a full release cycle later, we can get rid of the special case rules used
      for official packages. Also, this allows us to drop ./debian at teh drop
      of a hart, and recreate it with an version that reflects the current
      state of the kernel sources. If people want to dump files into ./debian,
      we can come up with a different scheme to allow that, if such need can be
      Signed-Off-By: Manoj Srivastava's avatarManoj Srivastava <srivasta@debian.org>
    • Manoj Srivastava's avatar
      Get rid of the facility to patch kernel sources · 123d4875
      Manoj Srivastava authored
      The patch the kernel facility was adding complexity, and failing to
      provide the flexibility required for a generic patching facility. It used
      to be useful at one point, but in the modern parlance, witht he
      widespread use of distribute version control systems, and various
      facilities to manage source and patch them, the built in version was
      Signed-Off-By: Manoj Srivastava's avatarManoj Srivastava <srivasta@debian.org>
  18. 08 Feb, 2009 1 commit
  19. 18 Oct, 2008 1 commit
  20. 13 Oct, 2008 1 commit
  21. 10 Oct, 2008 2 commits
  22. 10 May, 2007 1 commit
    • Manoj Srivastava's avatar
      Perform sanity checking of the stem argument. · a09081d0
      Manoj Srivastava authored
      * make-kpkg (main): Perform sanity checking of the stem argument. The
        stem, since it is the initial part of a package name must consist only
        of lower case letters (`a-z'), digits (`0-9'), plus (`+') and minus
        (`-') signs, and periods (`.').  It must be at least two characters
        long and must start with an alphanumeric character.
      Closes: Bug#422640
      * make-kpkg.8: Document the restrictions of the stem argument.
      git-archimport-id: srivasta@debian.org--lenny/kernel-package--devel--11.0--patch-13
  23. 04 May, 2007 1 commit
  24. 23 Oct, 2006 1 commit
  25. 15 Sep, 2006 1 commit
    • Manoj Srivastava's avatar
      Added a --verbose option to make-kpkg · 5c4f11b1
      Manoj Srivastava authored
      * make-kpkg.8: Document the new --verbose option
      * make-kpkg: Pass a V=1 option to the make so that commands are verbosely
        printed to the screen while executed.  This is very useful for
      git-archimport-id: srivasta@debian.org--etch/kernel-package--devel--9.0--patch-187
  26. 20 Aug, 2006 1 commit
  27. 19 Aug, 2006 1 commit
    • Manoj Srivastava's avatar
      Allow ~ in version numbers · 79372799
      Manoj Srivastava authored
      * make-kpkg (main): Allow ~ in version numbers
      * make-kpkg.8: Ditto.
      git-archimport-id: srivasta@debian.org--etch/kernel-package--devel--9.0--patch-176
  28. 19 Jul, 2006 2 commits
    • Manoj Srivastava's avatar
      clone targets to support newer default linux prefix · 5ce966f5
      Manoj Srivastava authored
      This change clones the target to support the newer linux prefix.  Also
      change some strings in make-kpkg with kernel-image too.
      * make-kpkg:
      *  kernel/ruleset/local.mk
      git-archimport-id: srivasta@debian.org--etch/kernel-package--devel--9.0--patch-165
    • Manoj Srivastava's avatar
      Fix version matching · ceef6b2c
      Manoj Srivastava authored
      * make-kpkg (main): Quote the $composite_version string so that the match
        does not get confused by regexp meta characters in the version.
      git-archimport-id: srivasta@debian.org--etch/kernel-package--devel--9.0--patch-164
  29. 28 Mar, 2006 1 commit
    • Manoj Srivastava's avatar
      Allow for presence of localversion · 8d9f8cc8
      Manoj Srivastava authored
      * make-kpkg (main): Since the advent of localversion, we no longer try
        for an exact match, just a substring one.
      git-archimport-id: srivasta@debian.org--etch/kernel-package--devel--9.0--patch-140
  30. 04 Jan, 2006 1 commit
  31. 28 Dec, 2005 1 commit
    • Manoj Srivastava's avatar
      typo fix · 74da857d
      Manoj Srivastava authored
      * make-kpkg: Typo fix
      git-archimport-id: srivasta@debian.org--etch/kernel-package--devel--9.0--patch-103
  32. 16 Dec, 2005 1 commit
    • Manoj Srivastava's avatar
      Minor bug fixes · aa1758af
      Manoj Srivastava authored
      * Makefile (check): Ignore failures in all image related postinsts --
        since check is run as non root, we cant load the debconf modules anyway.
      * make-kpkg (main): Die if there is no ./debian, and the first command is
        a module_blah target.
      * make-kpkg.8: Document the fact that modules_blah targets are not to be
        called when there is no ./debian directory
      git-archimport-id: srivasta@debian.org--etch/kernel-package--devel--9.0--patch-88
  33. 03 Dec, 2005 1 commit
    • Manoj Srivastava's avatar
      Allow building third party modules from header package directory · 67243ae4
      Manoj Srivastava authored
      It was pointed out to me that the ability to build third party modules
      using make-kpkg and linux kernel headers packages had broken with recent
      kernel packages, since the check for whether we were in a top level
      kernel source directory failed to take into account if we were in a
      header package directory, which is sufficient.
      Additionally, older kernel-package versions appear to want to run
      oldconfig in the headers package tree, which failed, since there was
      inadequate support for running oldconfig. This has also been fixed, since
      all we really need to depend on is a .config file.
      Finally, make-kpkg insists on there being a ./debian directory, and it
      makes sense to ship the directory in the source and header packages,
      since shipping it means that we also remove the need for kernel-package
      to be installed on the target system
      * kernel/ruleset/misc/checks.mk: The test for whether we are in a proper
        directory for running make-kpkg was incomplete, and failed to take into
        account if we were using a kernel headers package.
      * kernel/ruleset/modules.mk (modules-image modules_image): Change the
        dependency from configure to .config (so as not to tun oldconfig)
      * kernel/ruleset/modules.mk (modules): Ditto
      * kernel/ruleset/modules.mk (modules-config modules_config): Ditto
      * kernel/ruleset/modules.mk (modules-clean modules_clean): Ditto 
      * kernel/ruleset/targets/source.mk (install/$(s_package)): Arrange for
        ./debian directory to be shipped in the package.
      * kernel/ruleset/targets/headers.mk (install/$(h_package)): Arrange for
        ./debian directory to be shipped in the package.
      git-archimport-id: srivasta@debian.org--etch/kernel-package--devel--9.0--patch-75
  34. 09 Nov, 2005 1 commit
    • Manoj Srivastava's avatar
      Remove the old, decrepit FLAVOURS mechanism · 58a830d8
      Manoj Srivastava authored
      * kernel/ruleset/targets/source.mk (install/$(s_package)): No longer
        mention FLAVOURS, since that is now gone.
      * kernel/docs/README (so): Ditto
      * README (so): Ditto.
      * Makefile (DOCFILES): Ditto
      * make-kpkg: Ditto.
      * make-kpkg.8: Ditto
      * make-kpkg.fr.8: Ditto.
      * make-kpkg.es.8: Ditto.
      * Multi-Arch: Ditto.
      * _make-kpkg: Ditto.
      * kernel/ruleset/misc/README: Ditto.
      * kernel/docs/README.modules: Ditto.
      git-archimport-id: srivasta@debian.org--etch/kernel-package--devel--9.0--patch-70
  35. 02 Nov, 2005 1 commit
    • Manoj Srivastava's avatar
      New reorganization of the build mechanism · 41b1ba5b
      Manoj Srivastava authored
      	This is a major reorganization of the rules file that helps
       create kernel related packages. The crusty old mechanism has been
       removed, the targets are now streamlined, and the policy mandated
       dependencies are now called out into a separate file. This should allow
       a future enhancement to allow end users to override the behavior of
       kernel-package in a fine grained fashion. Also, separating out the
       variable setting for each arch into a separate file should facilitate
       the delegation of that file to the person responsible for kernel images
       for that architecture. And, separating out the policy mandated targets
       into fine grained double colon targets allows people to add in any
       additional make targets for a particular architecture, something long
      	One of the factors that made the build mechanism so complex was
       that the rules file had a dual purpose: Initially, when ./debian was not
       present or not populated, it was responsible for populating that, and
       then it was responsible for building the kernel packages, incorporating
       any user customizations.
      	Unfortunately, since Make reads all the commands at startup, it
       was difficult to incorporate any customizations, but the modularization
       of the rules file makes it possible to have two top level files, a
       minimal make file whose sole responsibility is to populate ./debian (and
       run clean even when ./debian does not exist), and which uses some of the
       same variable setting make snippets that the final top level Make file
       uses when it resides in ./debian. The task of deciding which top level
       makefile to use has now been relegated to /usr/bin/make-kpkg -- which,
       if there ./debian is empty or not present, first calls the minimal
       Makefile to populate it, and _then_ calls the real ./debian/rules file
       to perform the actual task that it was asked. This little intelligence
       in make-kpkg allows the minimal makefile, and ./debian/rules, to be far
       simpler, and allows them to conform to the standards my other Debian
       packages adhere to.
      	The goal of this release was to handle the bugs in the previous
       experimental release, but to create a set of packages indistinguishable
       from the ones created before. Pointedly, non-of the minor lacunae in the
       Debian kernel image postinst scripts have been addressed yet. Also, the
       build process is a little more verbose at the moment than it needs to be.
      * Makefile (DOCFILES): Removed package specific readme files (which
        really do not belong in kernel-package documentation, and added new
        docs that had been neglected.
      * kernel/Control (Build-Depends): Added build dependencies on po-debconf
        and gettext, in preparation for the forthcoming debconfication of the
        kernel packages.
      * kernel/Control (Recommends): Add recommendations for  po-debconf and
        gettext in the source package.
      * kernel/Control (Pre-Depends): Made the imagfe package pre-depend on
        debconf, since the preinst shall be using debconf to ask questions.
      * kernel/rules: Continued the process of skeletonizing the top level
        Makefile. Moved some more variables into their own files, and also
        moved the top level policy mandated targets into a separate file (so
        one does  not have to worry about proper dependency relations between
        those targets).
      * kernel/ruleset/architecture.mk: Converted this file into an
        skeleton/outline, to better allow delegation of responsibility for each
        architecture to the person in charge of kernel images for that arch.
      * kernel/ruleset/arches/README.txt: New file. Describes what the files in
        this directory do.
      * kernel/ruleset/arches/alpha.mk: New file to handle the architecture
        specific variables.
      * kernel/ruleset/arches/amd64.mk: New file to handle the architecture
        specific variables. 
      * kernel/ruleset/arches/hppa.mk: New file to handle the architecture
        specific variables. 
      * kernel/ruleset/arches/i386.mk: New file to handle the architecture
        specific variables. 
      * kernel/ruleset/arches/ia64.mk: New file to handle the architecture
        specific variables. 
      * kernel/ruleset/arches/m32r.mk: New file to handle the architecture
        specific variables. 
      * kernel/ruleset/arches/m68k.mk: New file to handle the architecture
        specific variables. 
      * kernel/ruleset/arches/mips.mk: New file to handle the architecture
        specific variables. 
      * kernel/ruleset/arches/mipsel.mk: New file to handle the architecture
        specific variables. 
      * kernel/ruleset/arches/ppc.mk: New file to handle the architecture
        specific variables. 
      * kernel/ruleset/arches/ppc64.mk: New file to handle the architecture
        specific variables. 
      * kernel/ruleset/arches/s390.mk: New file to handle the architecture
        specific variables. 
      * kernel/ruleset/arches/sparc.mk: New file to handle the architecture
        specific variables. 
      * kernel/ruleset/arches/uml.mk: New file to handle the architecture
        specific variables. 
      * kernel/ruleset/arches/xen.mk: New file to handle the architecture
        specific variables. 
      * kernel/ruleset/common/archvars.mk (REASON): Changed the wording for
        non-file targets.
      * kernel/ruleset/common/targets.mk: Made all the targets verbose. This is
        likely to be a temporary measure, but who knows.
      * kernel/ruleset/local-vars.mk: Made this file a skeleton/outline as
        well. All actual variable settings (apart from the stuff to clean) are
        now done in separate files (which allows us to have a minimal.mk in the
        first place).
      * kernel/ruleset/local.mk: This is yet another of the files that has been
        reduced to an outline. Apart from the buildpackage target, every thing
        else has been moved out to file in the targets subdirectory (the top
        level targets were already moved to common/targets)
      * kernel/scripts/kpkg-vercheck (main): Emit a warning if called with an
        empty argument.
      * make-kpkg (main): Create an alternate command (including an alternate
        rules file, the minimal one) in case ./debian has not yet been
        populated. This means that the default rules file for the main command
        is always fixed to be ./debian/rules, and we now just check
        /usr/share/kernel-package/rules for existence. If ./debian is not
        populated, the alternate command is built up, according to the
        following logic: if the target is clean or debian, we just set the
        alternate command accordingly. If the target is anything else, then the
        alternate command is set to be debian -- so that ./debian is properly
        populated first. So, id ./debian is not populated, and the command is
        clean or debian, just the alternate command is run. If the target was
        anything else (with an UN-populated ./debian), then first the alternate
        command is run to populate ./debian, then the normal command is run
        using the newly created ./debian.
      * kernel/ruleset/common/debconf.mk: New file, in preparation for the
        forthcoming debconfication.
      * kernel/ruleset/common/install_cmds.mk: New file, pulling these out of
        the local-vars file.
      * kernel/ruleset/common/pkgvars.mk: New file. This is what allows us to
        separate out the top level targets, by determining which packages need
        to be built.
      * kernel/ruleset/common/README: Describes what this directory is used for.
      * kernel/ruleset/minimal.mk: New file. This is the new top level file used when
        ./debian is not populated yet. The major tasks for this file is to run
        the clean target (which does not populate ./debian, indeed, can remove
        it if present), and to populate ./debian, if more complex tasks are to
        be performed. The population of ./debian requires that certain
        variables be set, and this file ensures we use the same makefile
        snippets that ./debian/rules shall use when actually performing the
        tasks, so there is no mismatch.
      * kernel/ruleset/misc/checks.mk: Various checks that would let the build
        process detect and abort on various error conditions.
      * kernel/ruleset/misc/config.mk: Various internal variable set based on
        defaults and the user configuration files, or from environment vars.
      * kernel/ruleset/misc/defaults.mk: This file sets default values for
        variables _before_ the user configuration files are read.
      * kernel/ruleset/misc/initrd.mk: This snippet uses hard coded version based
        heuristics to determine which set of tools would be viable for providing
        an initrd or initramdisk for the kernel being built, if initrd's are
        selected by the user as desired.
      * kernel/ruleset/misc/modules.mk: This file deals with setting up
        variables, looking at directories, and creating a list of valid third
        party modules available for the kernel being built.
      * kernel/ruleset/misc/patches.mk: This file deals with setting up
        variables, looking at directories, and creating a list of valid third
        party patches available for the kernel being built.
      * kernel/ruleset/misc/pkg_names.mk: This file sets up package names for
        the packages we can build (based on kernel version), the locations
        under ./debian where these packages shall be built, and the
        corresponding relative directory paths 
      * kernel/ruleset/misc/version_vars.mk: This file looks at the top level
        kernel Makefile, and extracts the components of the version string. It
        uses the kernel Makefile itself, so it takes into account everything
        the kernel Makefile itrself pays attention to. This file also
        calculated the obsolete Debian specific Flavour variable.
      * kernel/ruleset/modules.mk: This file contains the targets responsible
        for third party module interaction.
      * kernel/ruleset/targets/doc.mk: This file is responsible for creating
        the kernel-doc packages 
      * kernel/ruleset/targets/headers.mk: This file is responsible for
        creating the kernel-headers packages  
      * kernel/ruleset/targets/image.mk: This file is responsible for creating
        the kernel-image packages  
      * kernel/ruleset/targets/manual.mk: This file is responsible for creating
        the kernel-manual packages  
      * kernel/ruleset/targets/sanity_check.mk: This contains a sanity check
        that must be passed before creating a kernel package 
      * kernel/ruleset/targets/source.mk: This file is responsible forcreating
        the kernel-source packages  
      * kernel/ruleset/targets/target.mk: This file provides the commands
        commaon to a number of packages built, and also includes the files
        providing commands to build each of the packages we create. 
      git-archimport-id: srivasta@debian.org--etch/kernel-package--devel--9.0--patch-54