Marc,
I can probably be persuaded to check for fixed OpenBSD earlier (if we
have a version number that can guarantee a fix, the better). But it
would really help if you showed some minimal cooperation by proving
to me that, as you claimed, the install-sh script (which scriptversion?)
contained a
On Wed, Jan 02, 2008 at 10:48:34PM +0100, Ralf Wildenhues wrote:
> Hello Marc,
>
> Thanks for the report.
>
> * Marc Espie wrote on Thu, Dec 27, 2007 at 05:29:37PM CET:
> > On Thu, Dec 27, 2007 at 05:25:56PM +0100, Marc Espie wrote:
> > > the mkdir -p macro arbitrarily restricts itself to GNU mkd
On Jan 29, 2008 2:29 PM, Peter Stahlir <[EMAIL PROTECTED]> wrote:
> I want to install a python program at /usr/bin, for example /usr/bin/foo,
> where
> foo is a python script (and no, I don't want a foo.py).
dist_bin_SCRIPTS = foo
Or, if your script is actually preprocessed from some other sourc
Hi!
I want to install a python program at /usr/bin, for example /usr/bin/foo, where
foo is a python script (and no, I don't want a foo.py).
Should I do a
bin_PROGRAMS = foo,
where automake can't find a .o file, or
bin_PROGRAMS = foo
foo_SOURCES = foo,
where automake deletes my file, or
python_PYT
