From: Eric McDonald <mcdonald@phy.cmich.edu>
To: ejessen@adelphia.net
Cc: Skeezics Boondoggle <skeezics@q7.com>, xconq7@sources.redhat.com
Subject: Re: SDL Interface Development
Date: Sun, 31 Oct 2004 19:09:00 -0000 [thread overview]
Message-ID: <4185374F.8000101@phy.cmich.edu> (raw)
In-Reply-To: <20041031162812.SIHQ2188.mta11.adelphia.net@mail.adelphia.net>
Hi Erik, it's been a while since you've been heard from,
> 1. it should be OS-independent
All of it is.
> 2. it should be included inside the Xconq build. Otherwise, you can spend forever just trying to get
> everything to compile clean, before you can start any
> work.
Possibly. I think that between providing installers for precompiled
binaries for MinGW32 and providing source RPM's for Linux and other
platforms, there may not be a need to bundle everything together. But,
if you, Skeezics, and others would prefer a giant source tarball with
all the dep config scripts slaved to Xconq's one configure Script to
rule them all, I will consider it. I would still prefer to provide the
packages separately. Among other things, it will help to foster good
will with the developers of the various prereq software components.
> You've raised the barrier to entry so high, that
> nobody but the most fanatical will attempt to maintain
> the code. Which means the program will die out when
> the fanatics move on.
As I mentioned in earlier postings, it is not necessary to always keep
up with the latest and greatest. It is enough to set a standard as far
as the prereqs go, and then adhere to that standard. Upgrades to the
prereq packages only need to be done occasionally.
Eric
next prev parent reply other threads:[~2004-10-31 19:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 17:45 ejessen
2004-10-31 18:08 ` D. Cooper Stevenson
2004-10-31 18:57 ` Lincoln Peters
2004-10-31 19:09 ` Eric McDonald [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-30 23:28 Eric McDonald
2004-10-31 4:10 ` Lincoln Peters
2004-10-31 6:13 ` Eric McDonald
2004-10-31 6:34 ` Elijah Meeks
2004-10-31 7:34 ` Lincoln Peters
2004-10-31 18:39 ` Eric McDonald
2004-10-31 18:23 ` Eric McDonald
2004-10-31 6:54 ` D. Cooper Stevenson
2004-10-31 18:26 ` Eric McDonald
2004-10-31 16:28 ` Skeezics Boondoggle
2004-10-31 19:04 ` Eric McDonald
2004-10-31 19:04 ` Lincoln Peters
2004-10-31 19:50 ` Skeezics Boondoggle
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=4185374F.8000101@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=ejessen@adelphia.net \
--cc=skeezics@q7.com \
--cc=xconq7@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).