[Crossfire-wiki] [Crossfire DokuWiki] page changed: crossfire_release_guide

[no-reply_wiki at metalforge.org]

A page in your DokuWiki was added or changed. Here are the details:

Date        : 2007/03/06 01:21
User        : 
Edit Summary: 

@@ -1,8 +1,7 @@
  Directions below have 1.10.0 as the example release.  Directions of commands below presume you start in the top level SVN directory (the one that contains the arch, client, maps, server) for each phase (arch, client, maps, server)
  
- 
- == Arch & Maps ==
+ === Arch & Maps ===
  
  The process for both the arch and maps directory is the same - the only difference is the name of the files/paths.
  
    * Update the CHANGES in the branches/1.x to add a 1.10.0 changes line to mark changes before/after the branch.  Commit changed file:
@@ -58,9 +57,9 @@
    * Release of arch is now done
      
  
  
- == Client ==
+ === Client ===
  Start in branches/1.x
    * Update configure.in with new version number
    * re-run autoconf
    * Re-run configure (needed so new version number gets embedded in Makefiles)
@@ -139,6 +138,15 @@
      * Select crossfire-1.10.0.client.tar.gz from list of files, hit Add Files button.
      * Select Any for processor type, Source.gz for file type, hit Update/refresh.
      * Check box to send e-mail to users monitoring, hit button to send e-mail   
  
- == Client RPM Files ==
- Building the RPM is pretty straightforward.  It does require a system that actually uses RPM (like redhat).  Also, to some extent, the RPM is tied to the system it is built on, in terms of architecture and dependencies
+ === Client RPM Files ===
+ Building the RPM is pretty straightforward.  It does require a system that actually uses RPM (like redhat).  Also, to some extent, the RPM is tied to the system it is built on, in terms of architecture and dependencies.  For example, to build the 32 bit binaries, I boot my secondary system that is only 32 bit.
+ 
+   * Make sure you have already done the client archives above, since the rpm build requires them.
+   * Make crossfire-client.spec is up to date.  Not that it is likely some of the paths near the top of the file may need to be changed depending on your filesystem layout.
+   * Build the RPMs: ''rpmbuild -ba crossfire-client.spec''
+   * If there are errors, rpmbuild will tell you.
+   * Rpms would be put in _rpmdir/<architecture>
+   * Upload the RPMS, architecture is the architecture, type is rpm.
+ 
+ 


IP-Address  : 209.204.178.229
Old Revision: http://wiki.metalforge.net/doku.php/crossfire_release_guide?rev=1173080927
New Revision: http://wiki.metalforge.net/doku.php/crossfire_release_guide

-- 
This mail was generated by DokuWiki at
http://wiki.metalforge.net/