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 13:59:38 +0200 [thread overview]
Message-ID: <20150429115938.GN1993@hermes.click-hack.org> (raw)
In-Reply-To: <20150429135338.0aa92a70@md1em3qc>
On Wed, Apr 29, 2015 at 01:53:38PM +0200, Henning Schild wrote:
> On Wed, 29 Apr 2015 11:39:43 +0200
> Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:
>
> > is dh-autoreconf available on wheezy ?
>
> Sure.
>
> > If people work from a release, autoreconf is useless and has chances
> > to do more harm than good.
>
> So releases will contain the Makefiles and configure-scripts again?
No, Makefiles are generated by running the configure script. But the
configure script yes, only the git repository does not contain it or
maybe I misunderstood something.
>
> > If people do not work from a release, can we not expect them to run
> > autoreconf by themselves ?
>
> You are right, that is another way of looking at it. I was assuming
> that the rules should contain all necessary build steps, but i am not
> sure what the best practice is for debian-directories.
The thing is that debian allows to install very old versions of the
autotools. I would not want the default rule, to simply wreck the
autotools file because the user made the mistake of having old
versions of the autotools used by default, whereas the shipped ones
are fine.
--
Gilles.
next prev parent reply other threads:[~2015-04-29 11:59 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 ` [Xenomai] [PATCH 1/2] debian: add autoreconf to build rules Gilles Chanteperdrix
2015-04-29 11:53 ` Henning Schild
2015-04-29 11:59 ` Gilles Chanteperdrix [this message]
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=20150429115938.GN1993@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.