GNUstep binary installation

[Stefan Urbanek]

Hi,

Imagine a scenario:

User finds an application that he wants, and perhaps needs to use.

1. User downloads the Application and finds out that it requires something called 
"GNUstep".
2. User downloads GNUstep binary package
Note: User has a system without default package management or users does not 
use the package management, because he only knows how to use default system 
installation or has no permissions to install other software.
3. User installs GNUstep from a file manager (in KDE/Gnome/MS Windows) by 
launching a script or running an .exe file.
Note: no configuration files editing should be required.
4. User installs the Application either by extracting contents of the 
downloaded package to GNUstep specific directory OR user launches application 
installation script OR user runs GNUstep package installer to install it.
5. User launches the Application through "GNUstep application launcher"
Note: GNUstep application launcher is any environment-specifi way of launching GNUstep 
applications. It can be GWorkspace or KDE menu or windows Start menu. Another alternative 
for "GNUstep launcher" can be a very simple application displaying only icons 
and labels for all .app bundles from */Applications directories. In this second 
alternative, only the launcher has to be accessible from KDE/Gnome/Windows menu, no all 
apps.

User shold not edit any .configuration files and user does not have to be root.

One analogy can be JRE and Java applications.

How can be that done? What is needed for that?

Stefan Urbanek
--
http://stefan.agentfarms.net

First they ignore you, then they laugh at you, then they fight you, then you 
win.
- Mahatma Gandhi