From: Rich Salz <rsalz@osf.org>
To: bengtk@damek.kth.se, byron@netapp.com, rc@hawkwind.utcs.toronto.edu
Subject: Re: autoconfig
Date: Wed, 2 Apr 1997 12:30:09 -0500 [thread overview]
Message-ID: <199704021730.MAA01905@sulphur.osf.org> (raw)
> Posix feels more "professional" than autoconfig. Perhaps I'm just very vain.
It's not vain, just very silly.
Until one standard is 100% of the "marketplace" that you wish to serve,
then leveraging well-understood, succesful, tools like FSF's autoconf
are the way to go.
This is my experience based on having developed and released several
software packages to the net at large.
/r$
next reply other threads:[~1997-04-02 23:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-02 17:30 Rich Salz [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-04-05 18:38 autoconfig Bengt Kleberg
1997-04-02 20:24 autoconfig Byron Rakitzis
1997-04-02 9:38 autoconfig Bengt Kleberg
1997-04-03 0:15 ` autoconfig Scott Merrilees
1997-04-03 3:14 ` autoconfig Warren Toomey
1997-04-01 23:52 autoconfig Alan Watson
1997-04-01 19:28 autoconfig Byron Rakitzis
1997-04-02 1:11 ` autoconfig Greg A. Woods
1997-04-02 8:32 ` autoconfig Stefan Dalibor
1997-04-02 2:20 ` autoconfig Scott Schwartz
1997-04-02 15:10 ` autoconfig Mark K. Gardner
1997-04-02 2:59 ` autoconfig David Luyer
1997-04-02 16:32 ` autoconfig Chet Ramey
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=199704021730.MAA01905@sulphur.osf.org \
--to=rsalz@osf.org \
--cc=bengtk@damek.kth.se \
--cc=byron@netapp.com \
--cc=rc@hawkwind.utcs.toronto.edu \
/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 NNTP newsgroup(s).