public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: "Mark A. Flacy" <mflacy1@comcast.net>
Cc: xconq7 <xconq7@sources.redhat.com>
Subject: Re: SDL interface thoughts
Date: Sat, 18 Dec 2004 03:11:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0412171358280.25350-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <87zn0cvp5c.fsf@comcast.net>

Hi Mark,

On 17 Dec 2004, Mark A. Flacy wrote:

> Yeah, last release June 2004.  Old indeed.

I was referring to how long Slackware has been around, and not 
when the last release was. To be honest, I was pleasantly 
surprised to discover that at least 1 person was still using it. 
In my perception, the distro faded alot after the Slackware vs. 
Redhat debate of the mid-90's. Other distros such as Suse, 
Mandrake, and Debian seemed to displace it in the competition with 
Redhat.

> I'm sure that RPMs go over real well with the Debian crowd too.

Well, if there is some implication that I am RPM-centric, the 
truth is that I'm not. If you look through the list archives, you 
can find several places where I expressed a desire to find 
packagers for not only other Linux distros, but the BSD's and 
other Unixes as well. I also said that I would look into making 
debs myself, if someone could not be found to do it. As it turns 
out, the present maintainer of the Xconq 7.4.1 packages for Debian 
has volunteered to make packages for 7.5.0, once it is released. 
There was also some talk about making Gentoo ebuilds of the CVS 
snapshots that I occasionally release on Sourceforge.

The reason why Xconq has RPM packages of its prereleases is quite 
simple:
(1) I develop on a Fedora Core system; I used to develop on a 
Mandrake 8/9 system. Both distros use the Redhat package manager. 
It is a matter of convenience to release RPM packages.
(2) I have not yet had time to develop the necessary packager 
files for things such as Debian or Gentoo (or Slackware). It is on 
my list of things to do.

> As a Slackware user myself, I don't expect you to provide Slackware
> packages.  I would expect the source tar balls to be fairly straightforward
> to build, with perhaps some dependency information in the README or in the
> autoconf messages.

If "./configure --help" is a bit too concise, please let me know 
what sort of additional documentation would be nice. I think that 
'doc/INSTALL' also talks about the config options, but it hasn't 
been updated in a while.

> You may wish to look at http://asic-linux.com.mx/~izto/checkinstall/ if you
> ever were to start creating other distribution's packages for XConq.  It
> can make RPMs too, for that matter.

Thanks for the URL. I will look at it tonight.
I would still be concerned about testing the packages on the 
other distros though.

Eric

P.S. I haven't forgotten the Forth implementation that you (IIRC)  
suggested for a Xconq interpreter last year. Seeing as Xconq 
doesn't have as many developers as it could have, I've been far 
too busy with other things to give it any more consideration.

  reply	other threads:[~2004-12-17 19:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22  4:10 mskala
2004-11-22  5:53 ` Eric McDonald
2004-11-22  7:23   ` mskala
2004-11-22 19:02     ` Eric McDonald
2004-12-17 19:17       ` Mark A. Flacy
2004-12-18  3:11         ` Eric McDonald [this message]
2004-12-19  3:31         ` Eric McDonald

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=Pine.LNX.4.44.0412171358280.25350-100000@leon.phy.cmich.edu \
    --to=mcdonald@phy.cmich.edu \
    --cc=mflacy1@comcast.net \
    --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).