Mail Archives: djgpp-workers/1999/05/16/15:23:10
Eli Zaretskii wrote:
> I doubt it would be easy to come up with lists of such groups, except,
> maybe, in the case of the compiler and Binutils. Even for the
> compiler, there are all kinds of questions with no easy answers, like
> do they need Make, or Patch, or GDB (these are all "C development"
> tools).
When I was designing LBInstDJ's scripting, I resulted just in two groups
-
according to zip-picker, "basic execution environment" and "C
development".
(At first there were two other groups - "C+ development" and
"Objective-C
development" but they were not useful, just another name to gpp*b.zip
and
obj-c compiler). So my idea is to have these two groups and a many
ungrouped
but related zips. LBInstDJ would handle groups, autoexec.bat and provide
turbo vision front end for newbies with Borland background, UNIX and
GNU gurus would use "zippo -i something" - zippo would handle zips. What
about it? (However, I still have not decided, should LBInstDJ do just
first time install or provide front-end for all zippo's functions?
Opinions welcome.)
> So I would suggest to abandon the desire to make it both flexible and
> fool-proof, and instead come up with 2-3 basic packages, e.g. "just
> C", "just C and C++"; and for Emacs, Perl, and the likes recommend
> that they download all the auxiliary tools as well (a list of just
> what ``all the auxiliary tools'' are would be nice).
LBInstDJ would be fool-proof for first-time install, zippo - flexible
for further management.
Laurynas Biveinis
- Raw text -