Difference between revisions of "GNUstep Installation Process"

From GNUstepWiki
Jump to navigation Jump to search
Line 5: Line 5:
 
GNUstep package creation automation project.
 
GNUstep package creation automation project.
  
* What ?: This is a project to digitilize the process of creating GNUstep environment for a perticular OS platform.  
+
* What?: This is a project to automate the process of creating GNUstep environment for a perticular OS platform.  
  
* Why ?:  
+
* Why?:  
** There are lots of time spent from experienced GNUsteppers to new GNUsteppers on compiling the source and this waste will keep happen again and again.
+
** Lots of time is spent by experienced GNUsteppers to assist new GNUsteppers with compiling the source, and this waste will continue to occur unless we resolve certain issues.
** Time should be spent on the GNUstep developement not on compling and packaging process.
+
** Time should be spent on GNUstep developement, and not on the compling and packaging process.
** Install/remove GNUstep easily encourge the deployment of GNUstep in corporate environment.
+
** Installation/removal of GNUstep easily encourges the deployment of GNUstep in corporate environments.
 
** The pacakge creation process can be reproduced easliy by others with commands.
 
** The pacakge creation process can be reproduced easliy by others with commands.
** Improve QA testing by making GNUstep instances quickly.
+
** Improves QA testing by generating GNUstep instances quickly.
  
 
Plan
 
Plan

Revision as of 00:15, 16 February 2005

Stefan Urbanek, please modify whatever you see fit, even delete this page.

GNUstep installation process should be and could be as simple as "pkg-inst GNUstep-1.0" across GNUstep supported OS plaforms. Given GNUstep's cross-platform declaration on application development activities, so should the application mangement activies cross-platform united. But in oder to get there, following need to be done.

GNUstep package creation automation project.

  • What?: This is a project to automate the process of creating GNUstep environment for a perticular OS platform.
  • Why?:
    • Lots of time is spent by experienced GNUsteppers to assist new GNUsteppers with compiling the source, and this waste will continue to occur unless we resolve certain issues.
    • Time should be spent on GNUstep developement, and not on the compling and packaging process.
    • Installation/removal of GNUstep easily encourges the deployment of GNUstep in corporate environments.
    • The pacakge creation process can be reproduced easliy by others with commands.
    • Improves QA testing by generating GNUstep instances quickly.

Plan

  • Introduce CPAM(Cross-Platform Application Management) tool implemented by TWW Inc. to GNUstep CPAD community
    • Cross-Platform is easier said then done becuase each platform's features are barriers for others.
  • Release GNUstep package source implemented by TWW CPAM.
    • I will release a working package source for others to try and review.
    • The package soruces can generate native package format for RHAS rpm,Solaris pkgadd and HP-UX depot formats.
  • Write tutorial on learning TWW CPAM.
    • I am willing to help/assist a few persons 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.


  • More details TBA once I get familiar with mediawiki.
  • 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(tj_yang at hotmail dot com), 
 I have been working as a system administator and I am intrested 
 to bring the work experience to work on this task. 
 Please email me if you have comment/questions. 
 
 For detail about TWW, please see http://www.thewrittenword.com, 
 I have used their CPAM at work to bring cross-platform open-source software support 
 nightmare under control. 
 All the TWW tools and sources of their supported packages are GPL open-source 
 free of charge but not their support labor.