Hi Karl,
Karl Berry wrote:
I just learned that in some circumstances automake will insert a COPYING
file if it's missing (albeit with a warning), e.g., at make dist? (I
didn't look into the precise details.)
This is a very old feature and according to NEWS it was actually
deprecated in
Hi Karl, Peter,
* Peter Johansson wrote on Fri, Dec 12, 2008 at 03:24:18AM CET:
Karl Berry wrote:
I just learned that in some circumstances automake will insert a COPYING
file if it's missing (albeit with a warning), e.g., at make dist? (I
didn't look into the precise details.)
Never at
Le 10 déc. 08 à 21:14, Ralf Wildenhues a écrit :
Hi Akim,
Hi!
* Akim Demaille wrote on Wed, Dec 10, 2008 at 10:21:50AM CET:
Ok. And these makes can be fooled to implement the feature by
computing
the file name at make-time instead of passing a litteral?
Not quite sure I follow here
On Thu, 11 Dec 2008, Duft Markus wrote:
There is a philosophical stance that the software we develop is
intended for the software users rather than the software developer.
There is a problem if build behavior is different for the user than
for the software developer.
Build behaviour wouldn't
Hey all,
I'm wondering if there is a best practice for getting paths such as
locaeldir or datadir into source code. As it stands now in the Makefile
I've got:
prefix= /usr/local
datarootdir= ${prefix}/share
localedir = ${datarootdir}/locale
To get localedir into a source file, I've got a
On Thursday 2008-12-11 21:38, Monty Taylor wrote:
Hey all,
I'm wondering if there is a best practice for getting paths such as
locaeldir or datadir into source code. As it stands now in the Makefile
I've got:
prefix= /usr/local
datarootdir= ${prefix}/share
localedir = ${datarootdir}/locale
To
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Monty Taylor on 12/11/2008 1:38 PM:
Hey all,
I'm wondering if there is a best practice for getting paths such as
locaeldir or datadir into source code.
Best practice is to use the Makefile to do the expansion into another file
that
