public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 0/3] Implement hello <-> libhello pattern
Date: Mon, 5 Feb 2018 22:56:42 +0100	[thread overview]
Message-ID: <20180205215642.GF6836@yssyq.radix50.net> (raw)
In-Reply-To: <20180125083851.5887-1-asmirnov@ilbers.de>

On Thu, Jan 25, 2018 at 11:38:48AM +0300, Alexander Smirnov wrote:
> This series intended to add Isar build dependencies between recipes.

Some comments on the hello / libhello themselves.


> [PATCH 1/2] Rename binary package to avoid correlations with Debian hello.
> [PATCH 2/2] Add dependency from 'libhello'.

Please remove the trailing dot from the subjects.


> diff --git a/debian/changelog b/debian/changelog
...
> +hello (0.2) unstable; urgency=low

I'd suggest to tag:

v0.1 7f35942 Add autotools
v0.2 ffca497 Add dependency from 'libhello'

Otherwise, Acked-by: Baurzhan Ismagulov <ibr@ilbers.de>.


> [PATCH] libhello: First implementation

> diff --git a/Makefile.am b/Makefile.am
...
> +DB2MAN = docbook-to-man

I think that should be in Build-Depends: (the same applies to hello).


> +man1_MANS = hello.1

I suggest say_hello.3.


> +clean-local:
> +	-$(RM) -f $(man1_MANS)

I suggest removing the leading "-" (the same applies to hello; not sure why I
used that at the time).


> diff --git a/debian/.control.swp b/debian/.control.swp

Please remove.


> diff --git a/debian/changelog b/debian/changelog
...
> +libhello (0.1) unstable; urgency=low

Suggest to tag v0.1 1671f02 libhello: First implementation.


> diff --git a/debian/control b/debian/control
...
> +Build-Depends: debhelper (>= 9), autotools-dev

Strictly speaking, autotools-dev is not needed. However, in that case the build
may fail due to timestamp mess after a git checkout (if configure.ac happens to
be newer than configure, the latter would try to rebuild itself).

Depending on autotools-dev workarounds that for the same build suite, but not
for a different one (configure generated on jessie would rebuild fine on
jessie, but possibly not on other version, since exactly the same autotools
versions are required).

That led to the following hack:

https://github.com/ilbers/isar/blob/2d56fc1242ef3e3041eb248942324eb67e9b1319/meta/recipes-devtools/buildchroot/files/build.sh#L17

I suggest:

* Dropping the autotools-dev build-dependency.

* Adding AM_MAINTAINER_MODE([disable]) to configure.ac to avoid rebuilding
  configure, Makefile.in, etc. For development, one may enable it with
  ./configure --enable-maintainer-mode.

* Dropping the mentioned touch hack.

That would apply also to hello.

That is documented in:

https://www.gnu.org/software/automake/manual/html_node/CVS.html#CVS
https://www.gnu.org/software/automake/manual/html_node/maintainer_002dmode.html#maintainer_002dmode


> diff --git a/debian/copyright b/debian/copyright
...
> +Copyright: 2016 ilbers GmbH

2018?


> diff --git a/debian/menu b/debian/menu

I don't think we need a GUI menu entry for libhello. Suggest dropping the file.


> diff --git a/hello.h b/hello.h
...
> +#ifndef __HELLO_H__

According to C99, identifiers that begin with an underscore are reserved
(typically for compiler or OS use). Suggest HELLO_H.


> diff --git a/hello.sgml b/hello.sgml
...
> +    <refentrytitle>HELLO</refentrytitle>
> +    <manvolnum>1</manvolnum>
...
> +    <refname>hello</refname>
...
> +    <title>EXIT STATUS</title>
> +
> +    <para><application>libhello</application> always returns zero.</para>

Suggest providing info applicable for say_hello(3).


As we have a backlog of patches and the issues are minor, feel free to create
github bugs for issues that would take longer and mention them as # TODO:
https://github.com/ilbers/isar/issues/NN in the code.


With kind regards,
Baurzhan.

      parent reply	other threads:[~2018-02-05 21:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25  8:38 Alexander Smirnov
2018-01-25  8:38 ` [PATCH 1/3] dpkg-base: Add dependecies between Isar recipes Alexander Smirnov
2018-02-05 19:40   ` Jan Kiszka
2018-02-06 10:10     ` chombourger
2018-02-06 20:25       ` Alexander Smirnov
2018-01-25  8:38 ` [PATCH 2/3] build.sh: Install newly built packages Alexander Smirnov
2018-01-31 19:39   ` Jan Kiszka
2018-01-31 19:55     ` Alexander Smirnov
2018-01-31 20:01       ` Jan Kiszka
2018-02-01  7:49         ` Benedikt Niedermayr
2018-02-01  8:07           ` Alexander Smirnov
2018-02-01 10:09             ` Benedikt Niedermayr
2018-02-01 11:37               ` Jan Kiszka
2018-01-25  8:38 ` [PATCH 3/3] libhello: Add libhello Alexander Smirnov
2018-01-25  9:01   ` Jan Kiszka
2018-01-25 10:11     ` Alexander Smirnov
2018-01-25 10:30       ` Jan Kiszka
2018-01-29 16:14 ` [PATCH 0/3] Implement hello <-> libhello pattern Henning Schild
2018-02-05 21:56 ` Baurzhan Ismagulov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180205215642.GF6836@yssyq.radix50.net \
    --to=ibr@radix50.net \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox