Difference: DebianPackaging (2 vs. 3)

Revision 32019-02-06 - squinney

Line: 1 to 1
 
META TOPICPARENT name="DocsForLCFGDevelopers"

Debian Packaging

Line: 7 to 7
 

Documentation and Guides

Added:
>
>
 

Standard Package Files

Line: 50 to 51
  An Example LCFG component
Changed:
<
<
The main parts that will need modifying are the Build-Depends and Depends. The automatic gathering of dependencies is not as extensive as with RPMs, in particular all Perl or Python module dependencies have to be worked out manually. The package repository can be queried using the apt-file tool or, for Perl modules, the dh-make-perl tool, e.g.
>
>
The source package information must always come first, after that there should be a Package section for each binary package that will be generated.

The main parts that are likely to need modifying are the Build-Depends and Depends. The automatic gathering of dependencies is not as extensive as with RPMs, in particular all Perl or Python module dependencies have to be worked out manually. The package repository can be queried using the apt-file tool or, for Perl modules, the dh-make-perl tool, e.g.

 
% dh-make-perl locate LWP::UserAgent
Line: 62 to 65
 LWP::UserAgent is in libwww-perl package
Changed:
<
<
One notable difference between Debian and Redhat is that on Debian you can only depend upon packages, it's not possible to depend on file paths, e.g. /usr/bin/foo or perl module names, e.g. perl(Foo::Bar)
>
>
One notable difference between Debian and Redhat is that on Debian you can only depend upon the names of packages, it's not possible to depend on file paths, e.g. /usr/bin/foo or perl module names, e.g. perl(Foo::Bar)
 

debian/changelog

Changed:
<
<
This is not created by the gendeb command. Once the debian sub-directory exists for a project the debian/changelog file will be managed by the LCFG buildtools. When a version is tagged (using major, minor or micro) it will be updated accordingly, similarly when a =dev command (e.g. devpack, devrpm, devdeb) is used an entry will be added to the exported copy (your svn working copy will be untouched). Note that this changelog is for the Debian package and does not contain a log of the source changes, those are stored in the separate ChangeLog file which will usually be installed as part of the package.
>
>
This file is not created by the gendeb command. Once the debian sub-directory exists for a project the debian/changelog file will be managed by the LCFG buildtools. When a version is tagged (using major, minor or micro) it will be updated accordingly, similarly when a =dev command (e.g. devpack, devrpm, devdeb) is used an entry will be added to the exported copy (your svn working copy will be untouched). Note that this changelog is for the Debian package and does not contain a log of the source changes, those are stored in the separate ChangeLog file which will usually be installed as part of the package.
  To ensure a valid name and email address are inserted into the debian/changelog set DEBFULLNAME and DEBEMAIL environment variables, e.g.
Line: 105 to 108
 

debian/docs

Added:
>
>
Sometimes a project supplies extra documentation files which are not installed as part of the standard build/install process. To get those files included in the package you need to add them to the debian/docs file, that will typically already exist and, at least, include the ChangeLog.
 

debian/manpages

Most manpages will be generated and installed as part of the build process (i.e. using CMake) but if you have extras that need to be generated using a tool like pod2man then this can be be done by extending the dh_installman target like this:

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback