Difference between revisions of "GNUstep Installation Process"

Revision as of 12:15, 18 February 2005

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 united across OS platform.

For "pkg-inst GNUstep-1.0" details, please see http://mediawiki.gnustep.org/index.php/Package_management

@@ Line 1: / Line 1: @@
-Stefan Urbanek, please modify whatever you see fit, even delete this page.
-Given GNUstep's cross-platform declaration on application development activities, so should the application mangement activies cross-platform united.
+GNUstep installation process should be and could be as simple as "pkg-inst GNUstep-1.0" across GNUstep supported OS plaforms.
-GNUstep installation process should be and could be as simple as "pkg-inst GNUstep-1.0" across GNUstep supported OS plaforms. But in oder to get there, following need to be done.
+Given GNUstep's cross-platform declaration on application development activities, so should the application mangement activies united across OS platform.
-GNUstep package creation automation project.
-* What?: This is a project to automate the process of creating GNUstep environment for a perticular OS platform.
+For "pkg-inst GNUstep-1.0" details, please see http://mediawiki.gnustep.org/index.php/Package_management
-* 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 can be better spent on GNUstep developement, and not on the compling and packaging process.
-** Easy installation and removal of GNUstep encourges the deployment of GNUstep in corporate environments.
-** The softare adn pacakge creation processes can be reproduced easliy by others with simple commands.
-** Improves QA testing by generating GNUstep bug fixed 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 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 paragrah can be deleted later.
-  In this paragrah, I just want to make sure above out of nowhere 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 interested
-  to bring the CPAM experience to work on this project. I promised myslef to digitalize the
-  compiling process when "Adam Fedor" was kindly answer my emails regarding to the compiling issues
-  I econcuntered.
-  Please email me if you have comment/questions.
-  For detail about TWW, please see http://www.thewrittenword.com.
-  I have used CPAM tool at work to bring cross-platform open-source software support
-  nightmare under control. TWW CPAM tool is battle field tested ;)
-  All the TWW tools and sources of their supported packages are GPL open-source compliant.
-  They are freely avaiable(ftp://support.thewrittenword.com) but support labor and binary packages are not.

Difference between revisions of "GNUstep Installation Process"

Revision as of 12:15, 18 February 2005

Navigation menu

Search