bug#16623: PACKAGE vs PACKAGE_TARNAME

2014-02-02 Thread Peter Johansson
Hi infirit, On 02/03/2014 09:23 AM, infirit wrote: However I think there is a second bug in that adding no-define as an option still sets $PACKAGE and $VERSION. I checked the manual again, and it says no-define has the effect that PACKAGE and VERSION will not be AC_DEFINEd, i.e., not included

bug#16623: PACKAGE vs PACKAGE_TARNAME

2014-02-02 Thread infirit
On Sun, 2 Feb 2014 18:56:01 +0100 infirit wrote: > On Sun, 02 Feb 2014 23:21:03 +1000 > Peter Johansson wrote: > > [adding bug-automake] > > On 02/02/14 12:25, infirit wrote: > > > So for a project we wanted to make the tarball different from from > > > the package name. So we updated AC_INIT and

bug#16623: PACKAGE vs PACKAGE_TARNAME

2014-02-02 Thread infirit
On Sun, 02 Feb 2014 23:21:03 +1000 Peter Johansson wrote: > [adding bug-automake] > On 02/02/14 12:25, infirit wrote: > > So for a project we wanted to make the tarball different from from > > the package name. So we updated AC_INIT and added the tarname and > > indeed now the tarball generated ch

bug#16623: PACKAGE vs PACKAGE_TARNAME

2014-02-02 Thread Peter Johansson
[adding bug-automake] Hi infirit, On 02/02/14 12:25, infirit wrote: Hi, So for a project we wanted to make the tarball different from from the package name. So we updated AC_INIT and added the tarname and indeed now the tarball generated changes. However, we noticed that now the $PACKAGE vari