Browsing Korean translation

404.

You will need to adjust the <filename>changelog</filename>slightly in this case to reflect that this package is named <application>hello-debhelper</application> rather than just <application>hello</application>:

405.

hello-debhelper (2.1.1-1) dapper; urgency=low

* Initial release

-- Captain Packager &lt;packager@coolness.com&gt; Thu, 6 Apr 2006 10:07:19 -0700

406.

By using <application>debhelper</application>, the only things we need to change in <filename>control</filename> are the name (substituting <application>hello</application> for <application>hello-debhelper</application>) and adding <application>debhelper (&gt;= 4.0.0)</application> to the <emphasis>Build-Depends</emphasis> field for the source package. The <phrase>Ubuntu</phrase> package for <application>hello-debhelper</application> looks like:

407.

Source: hello-debhelper
Section: devel
Priority: extra
Maintainer: Capitan Packager &lt;packager@coolness.com&gt;
Standards-Version: 3.6.1
Build-Depends: debhelper (&gt;= 4)

Package: hello-debhelper
Architecture: any
Depends: ${shlibs:Depends}
Conflicts: hello
Provides: hello
Replaces: hello
Description: The classic greeting, and a good example
The GNU hello program produces a familiar, friendly greeting. It
allows non-programmers to use a classic computer science tool which
would otherwise be unavailable to them.
.
Seriously, though: this is an example of how to do a Debian package.
It is the Debian version of the GNU Project's `hello world' program
(which is itself an example for the GNU Project).
.
This is the same as the hello package, except it uses debhelper to
make the deb. Please see debhelper as to what it is.
[tab][tab]

408.

We can copy the <filename>copyright</filename> file and the <filename>postinst</filename> and <filename>prerm</filename> scripts from the <phrase>Ubuntu</phrase><application>hello-debhelper</application> package, as they have not changed since <xref linkend="basic-scratch"/>. We will also copy the <filename>rules</filename> file so we can inspect it.

409.

cp ../../ubuntu/hello-debhelper-2.1.1/debian/copyright .
cp ../../ubuntu/hello-debhelper-2.1.1/debian/postinst .
cp ../../ubuntu/hello-debhelper-2.1.1/debian/prerm .
cp ../../ubuntu/hello-debhelper-2.1.1/debian/rules.

410.

The last file we need to look at is <filename>rules</filename>, where the power of <application>debhelper</application> scripts can be seen. The <application>debhelper</application> version of <filename>rules</filename> is somewhat smaller (54 lines as opposed to 72 lines in the version from <xref linkend="basic-scratch-rules"/>).

411.

The <application>debhelper</application> version looks like:

412.

#!/usr/bin/make -f

package = hello-debhelper

CC = gcc
CFLAGS = -g -Wall

ifeq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
CFLAGS += -O2
endif

#export DH_VERBOSE=1

clean:
dh_testdir
dh_clean
rm -f build
-$(MAKE) -i distclean

install: build
dh_clean
dh_installdirs
$(MAKE) prefix=$(CURDIR)/debian/$(package)/usr \
mandir=$(CURDIR)/debian/$(package)/usr/share/man \
infodir=$(CURDIR)/debian/$(package)/usr/share/info \
install

build:
./configure --prefix=/usr
$(MAKE) CC="$(CC)" CFLAGS="$(CFLAGS)"
touch build

binary-indep: install
# There are no architecture-independent files to be uploaded
# generated by this package. If there were any they would be
# made here.

binary-arch: install
dh_testdir -a
dh_testroot -a
dh_installdocs -a NEWS
dh_installchangelogs -a ChangeLog
dh_strip -a
dh_compress -a
dh_fixperms -a
dh_installdeb -a
dh_shlibdeps -a
dh_gencontrol -a
dh_md5sums -a
dh_builddeb -a

binary: binary-indep binary-arch

.PHONY: binary binary-arch binary-indep clean checkroot
[tab][tab][tab]

413.

Notice that tasks like testing if you are in the right directory (<application>dh_testdir</application>), making sure you are building the package with root privileges (<application>dh_testroot</application>), installing documentation (<application>dh_installdocs</application> and <application>dh_installchangelogs</application>), and cleaning up after the build (<application>dh_clean</application>) are handled automatically. Many packages much more complicated than <application>hello</application> have <filename>rules</filename> files no bigger because the <application>debhelper</application> scripts handle most of the tasks. For a complete list of <application>debhelper</application> scripts, please see <xref linkend="appendix-debhelper"/>. They are also well documented in their respective <application>man</application> pages. It is a useful exercise to read the man page (they are well written and not lengthy) for each helper script used in the above <filename>rules</filename> file.