From: "Stewart V. Wright" <swright+gsl@physics.adelaide.edu.au>
To: gsl-discuss@sources.redhat.com
Subject: Re: preparing a new release (part 2)
Date: Thu, 08 Sep 2005 11:38:00 -0000 [thread overview]
Message-ID: <20050907223241.GC4520@anl.gov> (raw)
In-Reply-To: <20050907221713.GD30028@austin.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
G'day Linas,
* linas <linas@austin.ibm.com> [050907 17:18]:
> On Wed, Sep 07, 2005 at 06:14:41PM +0300, Andris Pavenis was heard to remark:
> >
> > -TESTS = test
> > -
> > check_PROGRAMS = test
> >
> > test_SOURCES = test.c
>
> This is a really bad name for a unix prgram. For, on my machine
>
> which test
>
> returns
>
> /usr/bin/test
I would not disagree too loudly on aesthetic grounds, but automake is
smart enough to preface the check_PROGRAMS with a ./ (or at least
enough of the directory tree) so there is no real problem in calling
it test, true or even false (if you wanted to be _really_ nasty to the
next generation of developers).
All in all the naming is not really a worry. I'm surprised about the
ordering of TESTS and check_PROGRAMS though...
Cheers,
S.
[-- Attachment #2: Type: application/pgp-signature, Size: 274 bytes --]
next prev parent reply other threads:[~2005-09-08 11:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050502191454.GB27571@LUNeutron.cc.lehigh.edu>
[not found] ` <20050516172339.GA18705@LUNeutron.cc.lehigh.edu>
[not found] ` <5F44E074-A8BA-48EA-88EE-452010AFD5F8@lehigh.edu>
[not found] ` <432269C6.6030102@lehigh.edu>
2005-09-06 11:23 ` Brian Gough
2005-09-06 13:53 ` Kevin Bube
2005-09-15 16:38 ` Brian Gough
2005-09-06 15:34 ` James Theiler
2005-09-06 16:44 ` Jonathan G. Underwood
2005-09-07 15:14 ` Andris Pavenis
2005-09-07 22:18 ` linas
2005-09-07 22:47 ` Philip Kendall
2005-09-07 22:52 ` linas
2005-09-08 9:16 ` Philip Kendall
2005-09-08 11:38 ` Stewart V. Wright [this message]
2005-09-08 11:38 ` Brian Gough
2005-09-07 22:47 ` linas
2005-09-09 21:31 ` Jeff Spirko
2005-09-09 14:59 ` preparing a new release keith.briggs
2005-09-15 16:53 ` Brian Gough
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050907223241.GC4520@anl.gov \
--to=swright+gsl@physics.adelaide.edu.au \
--cc=gsl-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).