FreeLists / openbeos / [openbeos] Re: Installer Proposal

[Kobi Lurie <k_lurie@xxxxxxxxxxxxxx>]

please make sure the installation shell script doesn't assume anything 
about the partition i'm going to install into
i had much trouble with apps that installed with a shell script and 
couldn't understand a partition name of two words, as in "bfs space".
also, how do u know what shell script we'll use.
what if someone doesn't want bash?
i think the installer should be able to have all the functions itself.
also, what if i've got a power failure in my house, exactly in the 
middle of installation?
what happens then?
how can we get the system back?
if i specify a directory to replace, then when the installation starts, 
it should backup to a file (say tar.bz2) and delete it afterwards.
this will make the process longer though. do you have a better idea?
and last thing: how exactly do dependencies work here? do we download 
what we need?
is there support for downloading optimized packages (compiled for 
athlon, i686, etc. when we move to gcc 3.2x) from the package server?
thanks.
btw, it's good that u brought up this subject, it's an important one.
do you think we can use it to install the entire os as well?
maybe from a base, and then download the necessary parts?
this might fit in a floppy. (kernel, app server, installer, ethernet, 
drivers)
hmmm.. maybe not.
this subject ignites alot of thoughts..
wish u luck in coding this.

Niels S. Reedijk wrote:

> Hello all,
>
> Attached is the first part of my installer proposal. I am willing to 
> code it if the idea is 
> supported by the rest of you lot. Here's a summary of the goals and 
> features of the 
> installer:
> - Provide a standard interface for customized installers
> - Create perfect uninstallers instantly
> - Support for dependencies
> - Centralized database
>
> It is a replacement for SoftwareValet. This means that any package 
> compiled for
> OBOS will install on all the different distributions derived from it. 
> Please read the
> first two paragraphs, as the third one already goes into somewhat more 
> detail.
> I'd like to get started on the library ASAP, however, I am eager for 
> your
> comments. 
>
> Niels S. Reedijk