From:	bpmurray*STUFFER*@socrates.cgl.ucsf.EDU (Bernard P. Murray, PhD)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: DJGPP: the future is... ?
Date:	Mon, 05 Apr 1999 13:44:34 -0700
Organization:	University of California, San Francisco
Lines:	28
Message-ID:	<bpmurray*STUFFER*-0504991344340001@mac-daddy.ucsf.edu>
References:	<199903260517 DOT AAA32193 AT envy DOT delorie DOT com> <36FBE6A6 DOT D1407A64 AT cableol DOT co DOT uk> <6y0O2.2463$MB3 DOT 4117 AT newsfeeds DOT bigpond DOT com>
NNTP-Posting-Host:	mac-daddy.ucsf.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In article <6y0O2.2463$MB3 DOT 4117 AT newsfeeds DOT bigpond DOT com>, "Johan Venter"
<jventer AT writeme DOT com> wrote:


> Also, the installation needs work. It need not be constricting. A program
> that checks the current directory for DJGPP packages (how about a slightly
> modified zip or tar format that it can use to identify them with?). Once it
> has found all the packages, maybe show the user a list of the packages
> (excluding the base ones) that can be installed. After this, install them.
> Maybe have a specific install file contained in each package, kind of like a
> makefile, that would allow the install program to decide on what (if any)
> extra settings/environment variables that need to be setup to get the
> package working????
> I don't know....I'm rambling.....just a thought.
> Johan Venter (aka sphinX)

Sounds like you'd like something like Redhat's RPM.
I wonder if that's possible? (I know that RPM is
Open Source).  The bad news is that all the DJGPP
files would have to be packaged appropriately.
The good news is that the dependencies would be
taken care of and so the frequent problems with
C++, RHIDE, Allegro etc. installations shouldn't occur
any more.  Hmmmmm...
     Bernard
-- 
Bernard P. Murray, PhD
Dept. Cell. Mol. Pharmacol., UCSF, San Francisco, USA

- Raw text -