to
> > >recommend that packagers run autoreconf on build. Their reasons
> > >are given here and seem to be good ones:
> > >
> > >https://wiki.debian.org/Autoreconf
> > >
> > >In the interests of fairness I can think of two drawbacks too:
> > >
&
Richard W.M. Jones wrote:
> I notice that Debian recently [since July 2014] started to recommend
> that packagers run autoreconf on build. Their reasons are given here
> and seem to be good ones:
>
> https://wiki.debian.org/Autoreconf
I've been arguing in favor of such a
On Sat, Jan 24, 2015 at 07:42:20PM +0100, Ralf Corsepius wrote:
> On 01/24/2015 03:14 PM, Richard W.M. Jones wrote:
> >
> >I notice that Debian recently [since July 2014] started to recommend
> >that packagers run autoreconf on build. Their reasons are given here
> &
On Sat, 24 Jan 2015 19:42:20 +0100, Ralf Corsepius wrote:
> In many other cases autoreconf can cause subtile and hard to find
> issues. In complex cases, it doesn't work at all.
Especially the former can be troublesome if they don't cause a build
to fail. For example, it can lead to issues such
On 01/24/2015 03:14 PM, Richard W.M. Jones wrote:
I notice that Debian recently [since July 2014] started to recommend
that packagers run autoreconf on build. Their reasons are given here
and seem to be good ones:
https://wiki.debian.org/Autoreconf
In the interests of fairness I can think of
I notice that Debian recently [since July 2014] started to recommend
that packagers run autoreconf on build. Their reasons are given here
and seem to be good ones:
https://wiki.debian.org/Autoreconf
In the interests of fairness I can think of two drawbacks too:
- newer versions of
