rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: culliton@srg.af.mil (Tom Culliton x2278)
To: byron@archone.tamu.edu, rc@archone.tamu.edu
Subject: Re: configuration parameters
Date: Fri, 14 Feb 1992 12:25:06 -0600	[thread overview]
Message-ID: <9202141325.aa10591@ceres.srg.af.mil> (raw)

I'd like to agree with Chris on this and disagree with who ever
suggested using imake.  Having the configuration parameters in the make
file, as they are now, works beautifully.  As matters stand I copy
"Makefile" to "makefile" edit the configuration options in that and go.
I never even have to touch any of the original files (aside from
applying patches from Byron ;-) ).

This is utterly painless and shows an absolutely incredible level of
portability.  Having ported more packages than I care to count to
various machines, rc is probably the cleanest.  Most packages get
checked into RCS the minute they're unbundled so we can track the
changes necessary just to get them running, not so with rc!

As to Imake... While the concept is probably OK the execution generally
stinks.  I've never seen it work right yet.  Please don't inflict it on
us!

Tom


             reply	other threads:[~1992-02-14 18:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-02-14 18:25 Tom Culliton x2278 [this message]
  -- strict thread matches above, loose matches on Subject: below --
1992-02-16 19:58 Alan Hargreaves
1992-02-17 15:35 ` jew
1992-02-14 23:20 rjc
1992-02-14 19:01 Tom Culliton x2278
1992-02-14 14:15 Rich Salz
1992-02-14  5:19 Byron Rakitzis
1992-02-14  5:33 ` Chris Siebenmann
1992-02-14 17:41   ` Brendan Kehoe
1992-02-14 18:24     ` Chris Siebenmann

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=9202141325.aa10591@ceres.srg.af.mil \
    --to=culliton@srg.af.mil \
    --cc=byron@archone.tamu.edu \
    --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).