[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        : 2008/07/19 21:13
User        : 
Edit Summary: Add detail note regarding making of client RPMs.

@@ -140,9 +140,12 @@
      * 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.  For example, to build the 32 bit binaries, I boot my secondary system that is only 32 bit.
+ 
+ //The crossfire-client.spec file requires the crossfire-client crossfire-client-sounds, crossfire-client-images tarballs to be present in a /export/home/crossfire/Crossfire directory (_sourcedir).  /export/home/crossfire/RPM-TOP must also exist and contain a BUILD subdirectory.  If this is not satisfactory, the %define statements for _sourcedir _srcrpmdir, _rpmdir, and _topdir may need to be locally altered to suite, but do not commit changes to SVN as the SVN settings no doubt support the actual directories used by the official client release manager.//
  
    * 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''
@@ -150,8 +153,9 @@
    * Rpms would be put in _rpmdir/<architecture>
    * Upload the RPMS, architecture is the architecture, type is rpm.
  
  === Server ===
+ 
  Start in branches/1.x
    * Update configure.ac with new version number
    * Update ChangeLog file, putting in break for new version
    * re-run autoconf
@@ -221,8 +225,9 @@
      * 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
  
  ==== Final Notes ====
+ 
  After all the components are bundled up, an official announcement is sent to crossfire-announce at lists.real-time.com.  I usually use the announcement of the last release as a template.
    * Update 1.9.1 to 1.10.0
    * generate a sum of the files.  I put all of them in one directory, so it is just a simple ''sum *'' and remove any extra entries that shouldn't be there.
    * Same for md5sums - ''md5sum *''
@@ -234,8 +239,9 @@
  
  See also [[crossfire_compile_guide#microsoft_c_windows]] for requirements.
  
  == Client ==
+ 
    * get latest sources
    * open Visual Studio project file ''gtk/win32/GTKClient.dsw''
    * alter ''gtk/win32/config.h'' to set version number (line 92)
    * switch to 'Release' build mode
@@ -275,12 +281,13 @@
    * release
    * send notification (if not doing map release)
  
  == Map installer ==
+ 
    * from server code, run the ''make_win32/make_maps_nsi.pl'' file (syntax: ''make_maps_nsi.pl "Big World maps" ..\..\share\maps'' if you installed maps in share)
    * build generated .NSI file
    * ensure installer works fine
    * rename executable to ''crossfire-server-bigworld-maps-1.10.0.exe''
    * upload to Sourceforge
    * add to previous release
    * send notification
  


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

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