From: schwartz@groucho.cs.psu.edu
To: malte@techfak.uni-bielefeld.de
Cc: rc@archone.tamu.edu
Subject: Re: to imake or not to imake
Date: Fri, 14 Feb 1992 14:52:05 -0600 [thread overview]
Message-ID: <92Feb14.155212est.2538@groucho.cs.psu.edu> (raw)
In-Reply-To: Your message of "Fri, 14 Feb 92 15:26:59 EST." <9202142026.AA05683@dahlie.techfak.uni-bielefeld.de>
| I don't want to start any religious wars, but imake -once set up correctly-
| usually shortens installation procedures to "imkmf; make install", especially
| if the sources are as portable as rc is.
But setting up imake is much harder than just setting up rc. And it is
different for every package! One directory full of imake config files
for InterViews, one for X11, one for Modula-3, etc, etc, etc. And even
when you have all that stuff straightened out, you gain nothing over
what we have now: editing a Makefile to comment out a couple of
defines verses editing an Imakefile to comment out a couple of
defines... where's the win? Keep simple things simple, please!
next prev parent reply other threads:[~1992-02-14 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-02-14 20:26 malte
1992-02-14 20:52 ` schwartz [this message]
1992-02-14 21:21 ` Chris Siebenmann
1992-02-14 21:37 ` jew
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=92Feb14.155212est.2538@groucho.cs.psu.edu \
--to=schwartz@groucho.cs.psu.edu \
--cc=malte@techfak.uni-bielefeld.de \
--cc=rc@archone.tamu.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).