Citát "M. Uli Kusterer" <[EMAIL PROTECTED]>: <snip>
> Another thing to take into consideration is > consistency among installers. I.e. eventually, a > GNUstep desktop will need to be able to install > itself. Since Installer.app depends on GNUstep, > you'd need a Live CD to run the installer from, > and the installer would have to be flexible > enough to install an entire Linux (maybe through > a .deb or .rpm) onto another drive, without write > access to the disk, etc. > No way to install GNUstep like that. "I do not want to reboot my computer to have that thing." > Without a Live-CD, we'd need an installer that > works completely without a GNUstep installation, > or which can work with some sort of > "GNUstep-Light" compiled into it (like > WindowMaker's setup app, which looks steppish, > but isn't dependent on GNUstep). I don't think > Installer.app should be implemented like this, > but if you find that some parts could easily be > implemented as a plain C installer library, that > would help the person who eventually has to code > the non-live installer. You mean a very simple, host environment native, 'GNUstep bootstrap/installer'? I would not go with the "GNUstep light" path as this can add more weight into the downloaded package. Using native installation mechanisms has several advantages: - users are familiar with them (they do not jump into something unknown) - already provides installation code - one has to provide only information about the installation (configuration scripts can be added) On the other hand, there is a disadvantage. That is that each environment has to have its own bootstrap installer which is non-portable. However, if we can manage to convert some custom GNUstep Environment installation instructions (wizard steps?) to native installer instructions, that can simplify creation of installers. Btw. how Java R.E. installers look like and work on different systems? Perhaps that should be a place where we can look, learn and improve. Maybe the one who is going to create the GNUstep Environment installer should try to install Java (or other analogous package) on several environments to see how it works there. GNUstep is not different in this, or at least it should be not, I think. Regards, Stefan Urbanek -- http://stefan.agentfarms.net First they ignore you, then they laugh at you, then they fight you, then you win. - Mahatma Gandhi
