X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date:message-id:subject
	:from:to:content-type;
	bh=K0uymUbZVbauTE5jcbvBoVG5ht09vij95OBAhZorplQ=;
	b=d2TqUFonVz2WhTgH1TFQddZzwAbNyqPI/t8RI73/38V9tFHMIa+jwsLu7YSZndT6x+
	z7kcGl3xgBPC9UNK2bmqY5ntzOlncgKNukmubKS71lmShjgPs2XNCwZ0ZtTt7LQWAZQe
	sNJPKopEGXfVC6j85Ns6annHPF9wFrGbcqkjSMfzVBK+n61hgES0EmQ+msOWpZcWrnH3
	BAicbSsZe9h+RJJ9jPq5x6vo6L9YSqKoX8SEFthbV6pg2eaLW1jYVfkWL1HbpxokDzCe
	0wCDMkLrid2vuaOyJf6JHa7XMjCdXQMkZZez6V/67LVqFKbWhBPyp6Xna1HTT23pExUN
	ziVg==
MIME-Version:	1.0
X-Received:	by 10.202.214.146 with SMTP id n140mr26415948oig.2.1442477326893;
	Thu, 17 Sep 2015 01:08:46 -0700 (PDT)
Sender:	svenn DOT bjerkem AT gmail DOT com
In-Reply-To:	<alpine.DEB.2.11.1509162231560.30298@nimbus>
References:	<alpine DOT DEB DOT 2 DOT 11 DOT 1509031356150 DOT 13201 AT nimbus>
	<55E8773B DOT 9000902 AT jump-ing DOT de>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1509031846370 DOT 7163 AT nimbus>
	<55E8831A DOT 8050307 AT jump-ing DOT de>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1509032004020 DOT 10628 AT nimbus>
	<55E891FA DOT 2010509 AT jump-ing DOT de>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1509032039300 DOT 14871 AT nimbus>
	<55E8AE6C DOT 2090304 AT jump-ing DOT de>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1509040031270 DOT 1962 AT nimbus>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1509041040130 DOT 2971 AT nimbus>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1509162004460 DOT 3909 AT lichen>
	<55F9C1BF DOT 9030603 AT jump-ing DOT de>
	<CAGde_xM4LLVK0v9HCfmhW+z+tnC1Z85A9QRjqWoODeq7OZc6mw AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1509162157140 DOT 25389 AT nimbus>
	<CAGde_xP_yGreyviKkkdxXpY2pANdgBtpcLt14_ZiawA2r_ECvA AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1509162231560 DOT 30298 AT nimbus>
Date:	Thu, 17 Sep 2015 10:08:46 +0200
X-Google-Sender-Auth:	5O0MR4Zyat0Mi2IA-8ZAc5cWfJs
Message-ID:	<CAGde_xPsE32R-5xm3dc=3tSB2eeL2upK3Oaoo3zbOAf9SOpuug@mail.gmail.com>
Subject:	Re: [geda-user] New experimental netlist features
From:	"Svenn Are Bjerkem (svenn DOT bjerkem AT googlemail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user <geda-user AT delorie DOT com>
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

--001a113ad68eaa8d28051fecec5c
Content-Type: text/plain; charset=UTF-8

On 16 September 2015 at 22:49, Roland Lutz <rlutz AT hedmen DOT org> wrote:

> Given that this had worked flawlessly, is there even a reason for an
> "autogen.sh" script nowadays?  Or could we just replace it with an
> "autoreconf -if" invocation?



Based on my experience from other projects, if an 'autogen.sh' exist, I
will always run that script. I have always assumed that this is the
build-from-source starting point as seen by the developers. Tar-balls
usually come with a working 'configure' script, but that is seldom the case
for pristine source checkouts.

'autoreconf -if' is a command you have to know about. It isn't shining as
an executable file after a ls -l like autogen.sh is. If 'autoreconf -if'
will work in 'any' project based on autoconf, I will probably have to
rethink my default habit when entering the source of an unknown project.

I see autogen.sh as an explicit starting point for new people entering the
source.

-- 
Svenn

--001a113ad68eaa8d28051fecec5c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On 16 September 2015 at 22:49, Roland Lutz <span dir=3D"ltr">&lt;<a href=3D=
"mailto:rlutz AT hedmen DOT org" target=3D"_blank">rlutz AT hedmen DOT org</a>&gt;</span>=
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">Given that this had worked flawle=
ssly, is there even a reason for an &quot;autogen.sh&quot; script nowadays?=
=C2=A0 Or could we just replace it with an &quot;autoreconf -if&quot; invoc=
ation?</blockquote></div><br><br></div><div class=3D"gmail_extra">Based on =
my experience from other projects, if an &#39;autogen.sh&#39; exist, I will=
 always run that script. I have always assumed that this is the build-from-=
source starting point as seen by the developers. Tar-balls usually come wit=
h a working &#39;configure&#39; script, but that is seldom the case for pri=
stine source checkouts.<br><br></div><div class=3D"gmail_extra">&#39;autore=
conf -if&#39; is a command you have to know about. It isn&#39;t shining as =
an executable file after a ls -l like autogen.sh is. If &#39;autoreconf -if=
&#39; will work in &#39;any&#39; project based on autoconf, I will probably=
 have to rethink my default habit when entering the source of an unknown pr=
oject.<br><br></div><div class=3D"gmail_extra">I see autogen.sh as an expli=
cit starting point for new people entering the source.<br></div><br>-- <br>=
<div class=3D"gmail_signature">Svenn</div></div>

--001a113ad68eaa8d28051fecec5c--

- Raw text -