From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Henning Schild <henning.schild@siemens.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] [PATCH 1/2] debian: add autoreconf to build rules
Date: Wed, 29 Apr 2015 11:39:43 +0200 [thread overview]
Message-ID: <20150429093943.GL1993@hermes.click-hack.org> (raw)
In-Reply-To: <5c789beff3ff2c2ef88fbe1a53342cb7ebc714b8.1430299655.git.henning.schild@siemens.com>
On Wed, Apr 29, 2015 at 11:32:42AM +0200, Henning Schild wrote:
> Add autoreconf steps to debian/rules and add required tools to build deps.
>
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
> ---
> debian/control | 2 +-
> debian/rules | 2 ++
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/debian/control b/debian/control
> index 2225648..54fc898 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -2,7 +2,7 @@ Source: xenomai
> Section: devel
> Priority: extra
> Maintainer: Xenomai <xenomai@xenomai.org>
> -Build-Depends: debhelper (>= 8), findutils (>= 4.2.28), autotools-dev, autoconf, automake, libtool
> +Build-Depends: debhelper (>= 8), findutils (>= 4.2.28),
> autotools-dev, autoconf, automake, dh-autoreconf
is dh-autoreconf available on wheezy ?
If people work from a release, autoreconf is useless and has chances
to do more harm than good.
If people do not work from a release, can we not expect them to run
autoreconf by themselves ?
--
Gilles.
next prev parent reply other threads:[~2015-04-29 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-29 9:32 [Xenomai] [PATCH 1/2] debian: add autoreconf to build rules Henning Schild
2015-04-29 9:32 ` [Xenomai] [PATCH 2/2] debian: change version number in changelog Henning Schild
2015-04-29 9:39 ` Gilles Chanteperdrix [this message]
2015-04-29 11:53 ` [Xenomai] [PATCH 1/2] debian: add autoreconf to build rules Henning Schild
2015-04-29 11:59 ` Gilles Chanteperdrix
2015-04-29 12:06 ` Henning Schild
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=20150429093943.GL1993@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=henning.schild@siemens.com \
--cc=xenomai@xenomai.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.