[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: make-kpkg strangeness



Hi,

        Have you read /usr/share/doc/kernel-package/README.modules? It
 states that:
======================================================================
        make-kpkg arranges to cd into each modules top directory,
 /usr/src/modules/<mod-name>/, and runs ./debian/rules <target>. 
 Additionally, the following information is provided in the
 environment:
 a) KVERS  Contains the kernel version
 b) KSRC   Contains the location of the kernel sources 
 c) KMAINT Contains the Name of the maintainer to pass to PGP
 d) KEMAIL Contains the email address of the maintainer

        Additionally, the following variables may also be present in the 
 environment:
   e) APPEND_TO_VERSION This contains a string to be appended to the 
                        EXTRAVERSION variable. This is already factored 
                        into the KVERS variable above.
   f) FLAVOUR Contains the flavour, if any, of the current
              kernel. This is already factored into the KVERS variable
              above.  Please note that FLAVOURS are now deprecated in
              preference to  APPEND_TO_VERSION
   g) INT_SUBARCH Contains the SUB arch if any if and only if the 
                  ARCH_IN_NAME variable has been set. I suspect that the
                  user wants the .deb names to be modified (but not the
                  kernel version or the location of the dir in which to
                  find modules if this is set. This is *NOT* factored
                  into KVERS above, and is there to be used at your
                  discretion. 
   h) UNSIGN_CHANGELOG  A boolean
   i) UNSIGN_SOURCE     A boolean
   j) ROOT_CMD          a program, like sudo or fakeroot
   k) root_cmd This is a misnomer. That variable actually holds arguments
               for dpkg, specifically, -uc -us -r<blah>, or any
               combination thereof, asd requested by the user. This
               may be set in the config file, so if this variable
               exists, it incorporates and over rides the env vars
               UNSIGN_CHANGELOG, UNSIGN_SOURCE, and ROOT_CMD

        Please have a look at the sample files for creating a
 dependent modules package, sample.module.rules and
 sample.module.control.

----------------------------------------------------------------------

	The targets called are:
 kdist_image    : Just the binary image of the module is created
 kdist          : generate the modules packages and sign them
 kdist_configure: configure the modules packages
 kdist_clean    : clean the modules source tree

----------------------------------------------------------------------

	The error message says that there is no target called
 kdist_image in the debian/rules file in the modules dir.

 	Please look at previously packaged modules (alsa modules come
 to mind) for examples.

	manoj
-- 
 "It is better for civilization to be going down the drain than to be
 coming up it." Henry Allen
Manoj Srivastava   <srivasta@debian.org>  <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


-- 
To UNSUBSCRIBE, email to debian-mentors-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: