Changes between Initial Version and Version 1 of MapGuideRfc57


Ignore:
Timestamp:
11/25/08 18:47:10 (16 years ago)
Author:
zspitzer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MapGuideRfc57

    v1 v1  
     1= !MapGuide RFC 57 -  Refining the linux build process and generating install packages =
     2
     3This page contains an change request (RFC) for the !MapGuide Open Source project.
     4More !MapGuide RFCs can be found on the [wiki:MapGuideRfcs RFCs] page.
     5
     6
     7== Status ==
     8
     9||RFC Template Version||(1.0)||
     10||Submission Date||(Date/Time submitted)||
     11||Last Modified|| Zac Spitzer [[Timestamp]]||
     12||Author|| Zac Spizter ||
     13||RFC Status||(draft)||
     14||Implementation Status||(pending)||
     15||Proposed Milestone||(e.g. 2.2)||
     16||Assigned PSC guide(s)||(when determined)||
     17||'''Voting History'''||(vote date)||
     18||+1||||
     19||+0||||
     20||-0||||
     21||-1||||
     22||no vote|| ||
     23
     24== Overview ==
     25
     26Currently the Linux build process is rather tricky and doesn't produce packages which can be redistributed. As part of this process
     27the older OEM packages in the source tree will be subsituted with packages that are already available within the distributions
     28
     29== Motivation ==
     30
     31Simplifying the build process will make it easier for both Linux users and developers to get involved with the MapGuide project.  Removing the
     32OEM components from the build will drastically reduce both the build time and complexity.
     33
     34== Proposed Solution ==
     35
     36Working in a sandbox, a new CMake based build system will be developed. This will include dependency checking and will aim to reduce the number of
     37OEM components required for the build. Some if not all of the OEM components will be substituted with the existing packages available within the normal
     38Linux environment.
     39
     40As part of the CMake build process RPM and Debian style packages will be produced.
     41
     42== Implications ==
     43
     44TBD
     45
     46== Test Plan ==
     47
     48Existing test plans will be used to test the outcome of this RFC
     49
     50== Funding/Resources ==
     51
     52Community Supported