Re: [PATCH 6/6] recipes-app/example-custom: add example on how to use dpkg-custom

[Henning Schild <henning.schild@siemens.com>]

Am Mon, 4 Sep 2017 18:40:20 +0300
schrieb Alexander Smirnov <asmirnov@ilbers.de>:

> On 08/30/2017 10:03 PM, Henning Schild wrote:
> > Issue:
> > It might not be clear to a user how to make use of the class
> > dpkg-custom.
> > 
> > Change:
> > Add an example that demonstrates some features.
> > 
> > Impact:
> > This patch does not change the behaviour of Isar. It addresses the
> > issue partially, documentation would also be useful.
> > 
> > Signed-off-by: Henning Schild <henning.schild@siemens.com>
> > ---
> >   .../example-custom/example-custom_0.1.bb           | 35
> > ++++++++++++++++++++++
> > meta-isar/recipes-app/example-custom/files/README  |  1
> > + .../recipes-app/example-custom/files/postinst      | 16
> > ++++++++++ 3 files changed, 52 insertions(+) create mode 100644
> > meta-isar/recipes-app/example-custom/example-custom_0.1.bb create
> > mode 100644 meta-isar/recipes-app/example-custom/files/README
> > create mode 100644
> > meta-isar/recipes-app/example-custom/files/postinst
> > 
> > diff --git
> > a/meta-isar/recipes-app/example-custom/example-custom_0.1.bb
> > b/meta-isar/recipes-app/example-custom/example-custom_0.1.bb new
> > file mode 100644 index 0000000..efa813e --- /dev/null
> > +++ b/meta-isar/recipes-app/example-custom/example-custom_0.1.bb
> > @@ -0,0 +1,35 @@
> > +# Sample application using dpkg-custom, which turns a folder
> > (${D}) of +# files into a .deb
> > +#
> > +# This software is a part of ISAR.
> > +
> > +DESCRIPTION = "Sample application for ISAR"
> > +MAINTAINER = "Your name here <you@domain.com>"
> > +DEBIAN_DEPENDS = "apt"
> > +
> > +SRC_URI = "file://README \
> > +	   file://postinst"
> > +
> > +inherit dpkg-custom
> > +
> > +do_populate_package() {
> > +	bbnote "Creating ${PN} binary"
> > +	echo "#!/bin/sh" > ${WORKDIR}/${PN}
> > +	echo "echo Hello ISAR! ${PN}_${PV}" >> ${WORKDIR}/${PN}
> > +
> > +	bbnote "Putting ${PN} into package"
> > +	install -v -d ${D}/usr/local/bin/
> > +	install -v -m 755 ${WORKDIR}/${PN} ${D}/usr/local/bin/${PN}
> > +
> > +	bbnote "Now copy ${FILESDIR}/README into package"
> > +	install -v -d ${D}/usr/local/doc/
> > +	install -v -m 644 ${WORKDIR}/README
> > ${D}/usr/local/doc/README-${P} +
> > +	bbnote "Now for a debian hook, see dpkg-deb"
> > +	install -v -m 755 ${WORKDIR}/postinst ${D}/DEBIAN/postinst
> > +
> > +	bbnote "Now for a fake config file"
> > +	echo "# empty config file" > ${WORKDIR}/${PN}.conf
> > +	install -v -d ${D}/usr/local/etc/
> > +	install -v -m 644 ${WORKDIR}/${PN}.conf
> > ${D}/usr/local/etc/${PN}.conf +}
> > diff --git a/meta-isar/recipes-app/example-custom/files/README
> > b/meta-isar/recipes-app/example-custom/files/README new file mode
> > 100644 index 0000000..6e2ce0f
> > --- /dev/null
> > +++ b/meta-isar/recipes-app/example-custom/files/README
> > @@ -0,0 +1 @@
> > +This is an example file that we get from FILESDIR in recipe.
> > diff --git a/meta-isar/recipes-app/example-custom/files/postinst
> > b/meta-isar/recipes-app/example-custom/files/postinst new file mode
> > 100644 index 0000000..a28afa3
> > --- /dev/null
> > +++ b/meta-isar/recipes-app/example-custom/files/postinst
> > @@ -0,0 +1,16 @@
> > +#!/bin/sh
> > +
> > +set -e
> > +
> > +if ! getent group isar >/dev/null; then
> > +	addgroup --quiet --system isar
> > +fi
> > +
> > +if ! getent passwd isar >/dev/null; then
> > +	useradd --system --gid isar --create-home \
> > +		--home /var/lib/isar --no-user-group \
> > +		--comment "My isar user" \
> > +		isar
> > +fi
> > +
> > +chown -R isar:isar /var/lib/isar
> >   
> 
> That's a good demo scenario. But probably it makes sense to
> demonstrate it on real use case, for example set default password for
> root. This anyway should be done, probably it's a good time :-)

Well unfortunately the root password is special. It is special because
everyone probably wants to set it, and i do not want people to start
abusing that example to do so.
And it is special because the configure-script sets it as well and the
question "how and when do custom packages get into the rootfs" has not
been decided yet. Once we have answered that question i would be happy
to provide patches that move all of the configure-script into hooks.

Henning