Mail Archives: djgpp-workers/1999/05/14/14:34:07
Hello.
Laurynas Biveinis wrote:
> BTW, do you group zips into units which provide some level of
> functionality, e.g. "C development" would include gcc*b.zip & co, or
> just keep them separated and require user to know which zips he must
> install for C, which for C++ and so on? In this case, your tool would be
> back-end for mine. And script file should be changed to reflect this.
Well, I think it should be able to do both, e.g. for installing a group of
files.
djgpppm -i --group emacs
or something similar. I think it should be very flexible. How about this
(in DJ's suggested format):
group: HugelyComplicatedPackage
zip: huge11b1.zip
zip: huge11b2.zip
zip: huge11b3.zip
...etc...
The installer will then have to work out the dependencies from the format
for each individual zip.
Right, I'm changing the name to zippo. djgpppm makes me wince every time I
write it now.
I'm a little pushed for time right now too. I thought I'd see what
everybody thought and work out the specification for the rest of the
program, before I actually start writing - unlike usual ;)
The front-end - back-end divide seems good, if you are happy with this
idea.
--
==========================================================================
Rich Dawe - 4th-year MSci Physicist @ Bristol University, UK
richdawe AT bigfoot DOT com, http://www.bigfoot.com/~richdawe/
==========================================================================
- Raw text -