Date: Tue, 18 May 1999 13:37:47 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Richard Dawe <richdawe AT bigfoot DOT com>
cc: DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Re: DJGPP installer [Was: Script language for installer]
In-Reply-To: <373EF957.6431AEC@bigfoot.com>
Message-ID: <Pine.SUN.3.91.990518133716.24330I-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 16 May 1999, Richard Dawe wrote:

> Eli Zaretskii wrote:
> > do they need Make, or Patch, or GDB (these are all "C development"
> > tools).
> 
> I can't imagine not having 'make' installed.

I suspect that most of those who use RHIDE only have Make because
Allegro cannot be built without it.

> Maybe a quick survey here and
> in c.o.m.d would yield a list of "expected" packages needed for C
> development, etc.?

A good idea, IMHO.  Perhaps a Web page could be set up where people
could report what they have installed.

DJ, can the zip picker be easily modified to maintain a data base that
would allow queries like this?

> This is where the distinction between 'requires' and 'depends-on' is
> important. The 'depends-on' would be the recommended list you speak of.

I was thinking beyond that.  I was thinking about making large zip
archives that include all these ``depends-on'' packages.  I think this
is better than put a list into a README and expect people to be
grown-ups.  Perhaps the FAQ experience made me a bit paranoiac about
this...