debbuild - Man Page

2005-2015 © Kris Deugau <kdeugau@deepnet.cx>

2015-2019 © Andreas Scherer <https://ascherer.github.io/>

2015-2019 © Neal Gompa ngompa13@gmail.com

2017-2019 © Datto, Inc. <https://datto.com>

Build .deb packages from RPM-style .spec files.

debbuild supports most package-building options rpmbuild does.

Build options with [ <specfile> | <tarball> | <source package> ]:

  -b.                        build from <specfile> ...
  -t.                        build from <tarball> ...
  -r.                        build from <source package> ...
        -.p      ... through %prep (unpack sources and apply patches)
        -.c      ... through %build (%prep, then compile)
        -.i      ... through %install (%prep, %build, then install)
        -.l      verify %files section
        -.a      ... source and binary packages
        -.b      ... binary package only
        -.s      ... source package only
  --rebuild (-rb)            build binary package from <source package>
  --recompile (-ri)          build through %install from <source package>
  --buildroot=DIRECTORY      override build root
  --short-circuit            skip straight to specified stage (only c,i)

Common options:

  -D, --define='MACRO EXPR'  define MACRO with value EXPR
  --with/--without FLAG      define build conditionals from FLAG
  -S, --scm=SCM              short for '--define "__scm SCM"'

debbuild-specific options:

  -i, --install              Unpack a .sdeb in the %_topdir tree
  --showpkgs                 Show package names that would be built.
  --nobuild                  Parse <specfile>, but do no processing

debbuild attempts to build Debian-friendly semi-native packages from RPM spec files, RPM-friendly tarballs, and RPM source packages (.src.rpm files).  It accepts most of the options rpmbuild does, and should be able to interpret most spec files usefully.  Perl modules should be handled via CPAN+dh-make-perl instead as it’s simpler than even tweaking a .spec template.

As far as possible, the command-line options are identical to those from rpmbuild, although several rpmbuild options are not supported:

 --clean
 --rmsource
 --rmspec
 --target

Some of these could probably be trivially added.  Feel free to send me a patch.  ;)

Complex spec files will most likely not work well, if at all.  Rewrite them from scratch – you’ll have to make heavy modifications anyway.

If you see something you don’t like, mail me.  Send a patch if you feel inspired.  I don’t promise I’ll do anything other than say “Yup, that’s broken” or “Got your message”.

The source package container I invented for debbuild, the .sdeb file, can be installed with debbuild -i exactly the same way as a .src.rpm can be installed with rpm -i.  Both will unpack the file and place the source(s) and .spec file in the appropriate places in %_topdir/SOURCES and %_topdir/SPECS respectively.

As with rpmbuild, debbuild makes some assumptions about your system.

• Either you have rights to do as you please under /usr/src/debian, or you have created a file ~/.debmacros containing a suitable “%_topdir” definition.

  Both rpmbuild and debbuild require the directories %_topdir/{BUILD,SOURCES,SPECS}.  However, where rpmbuild requires the %_topdir/{RPMS,SRPMS} directories, debbuild requires %_topdir/{DEBS,SDEBS} instead.  Create them in advance; some subdirectories are created automatically as needed, but most are not.

• /var/tmp must allow script execution – rpmbuild and debbuild both rely on creating and executing shell scripts for much of their functionality.  By default, debbuild also creates install trees under /var/tmp – however this is (almost) entirely under the control of the package’s .spec file.

• If you wish to --rebuild a .src.rpm file, your %_topdir for both debbuild and rpmbuild must either match, or be suitably symlinked one direction or another so that both programs are effectively working in the same tree.  (Or you could just manually wrestle files around your system.)

  You could symlink ~/.rpmmacros to ~/.debmacros (or vice versa) and save yourself some hassle if you need to rebuild .src.rpm packages on a regular basis.

debbuild deliberately does a few things differently from rpmbuild.

debbuild was written by Kris Deugau.  The present version was developed by Andreas Scherer, Neal Gompa, and others. It is available at <http://github.com/debbuild/debbuild>.

Funky Things Happen if you forget a command-line option or two.  I’ve been too lazy to bother fixing this.

Many macro expansions are supported, some are incompletely supported, some not at all.

The generated scriptlets don’t quite match those from rpmbuild exactly.  There are extra environment variables and preprocessing that I haven't needed (yet).

Documentation, such as it is, will likely remain perpetually out of date (in which way it follows in RPM’s tradition).

%_topdir and the five “working” directories under %_topdir could arguably be created by debbuild.  However, rpmbuild doesn't create these directories either.

rpm(8), rpmbuild(8), and pretty much any document describing how to write a .spec file.