Difference between revisions of "GNUstep Installation Process"

From GNUstepWiki
Jump to navigation Jump to search
m (add link)
 
(49 intermediate revisions by 9 users not shown)
Line 1: Line 1:
GNUstep package creation automation project/process.
+
At the moment, the ways available to install GNUstep is heavily dependent on the host operating system platform.  
  
* What: This is a project to digitilize the process of creating GNUstep environment for a perticular OS platform to install/remove GNUstep easily thus encourge the deployment of GNUstep in corporate environment. And the pacakge creation process can be reproduced easliy by others with commands.
+
==Installing from source code==
  
* Why: There are lots of time spent from experienced GNUsteppers to new GNUsteppers. Time should be spent on the GNUstep developement not on compling and packaging process.
+
If you wish to install from source code, instructions are available from [http://www.gnustep.org/resources/documentation/User/GNUstep/gnustep-howto_toc.html GNUstep Howto] - and if you want to stay on the bleeding edge, check out point 7 on that page or Dennis Leeuw's [http://gnustep.made-it.com/BuildGuide/index.html GNUstep Build Guide for Unix Systems].
  
Plan
+
* latest instructions for [[Installation on Windows]]
 +
* latest instructions for [[Gorm Installation On Windows]]
 +
* latest instructions for [[Installation of 32bit GNUstep on 64bit Linux]]
  
* Introduce CPAM(Cross-Platform Application Management) tool implemented by TWW Inc. to GNUstep CPAD community
+
==Using your native packaging system==
** Cross-Platform is easier said then done becuase each platform's features are barriers for others.
 
  
* Release GNUstep package source implemented by TWW CPAM.  
+
Many platforms offer native GNUstep packages that may be installed in the same way that other software is commonly installed. Some information on platform-specific packages can be located at [[Platform_compatibility]].
  
    ** I will release a working package source for others to try and review.
+
==Some aspirations==
    ** The package soruces can generate native package format for RHAS rpm,Solaris pkgadd and HP-UX depot formats.
 
  
* Write tutorial on learning TWW CPAM.
+
GNUstep installation process could be and should be as simple as "pkg-inst GNUstep-1.0" across GNUstep supported OS plaforms.  
  ** I am willing to help/assist a few person to get familliar with TWW tools
 
      if they promise me to write up what they learned in a tutorial article.
 
      As you can see I am really not good on documenation work.
 
  
* Integrate GNUstep developement process with TWW CPAM.
+
Given GNUstep's cross-platform approach to application development activities, the application mangement activies should also be united across OS platforms.
  
* More details TBA once I get familiar with mediawiki.
+
For "pkg-inst GNUstep-1.0" details, please see [[Package_management]].
  
* Following lines can be deleted later. I just want to make above out of nohere text not treated as spam.
 
* My name is T.J. Yang, I have been working as a system administator for the past decade. I am intrested to work on this task. Please see the above plan to get this task done. Please leave your comment here. or use the discussion(which I don't know how to use it yet).
 
  
* For detail about TWW, please see http://www.thewrittenword.com,
+
Few notes: http://lists.gnu.org/archive/html/discuss-gnustep/2005-01/msg00381.html
  I have used their CPAM to bring  open-source  software under control.
 
  The TWW tools and sources of their supported packages are GPL open-source
 
  free of charge but not their support labor.
 

Latest revision as of 11:07, 29 October 2006

At the moment, the ways available to install GNUstep is heavily dependent on the host operating system platform.

Installing from source code

If you wish to install from source code, instructions are available from GNUstep Howto - and if you want to stay on the bleeding edge, check out point 7 on that page or Dennis Leeuw's GNUstep Build Guide for Unix Systems.

Using your native packaging system

Many platforms offer native GNUstep packages that may be installed in the same way that other software is commonly installed. Some information on platform-specific packages can be located at Platform_compatibility.

Some aspirations

GNUstep installation process could be and should be as simple as "pkg-inst GNUstep-1.0" across GNUstep supported OS plaforms.

Given GNUstep's cross-platform approach to application development activities, the application mangement activies should also be united across OS platforms.

For "pkg-inst GNUstep-1.0" details, please see Package_management.


Few notes: http://lists.gnu.org/archive/html/discuss-gnustep/2005-01/msg00381.html