[Crossfire-wiki] [Crossfire DokuWiki] page changed: user:kbulgrien

[no-reply_wiki at metalforge.org]

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

Date        : 2009/05/14 04:26
User        : kbulgrien
Edit Summary: Replace prerelease with release; update release guide outline; add snapshot term, and --release option significance.

@@ -285,24 +285,19 @@
    Proceed with the installation of the 3 packages? (Y/n) Y
    ...
    $ sudo urpmi makedepend cproto
  
- ======Pre-Release Guide (WIP)======
- 
- =====Pre-Release Preparation=====
+ ======Release Guide (WIP)======
  
  The directions use SVN trunk as the example release.  The instructions 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)
  
  This procedure assumes that release operations are done in the ''/home/devel/crossfire/rpmbuild'' directory.
  
  The RPMs build in this procedure may be installed by a user without using **sudo** or root permissions.  The RPMs will be build to install in the user's home directory (**${HOME}/usr/local/games/crossfire**).  This path is chosen so it is clearer how to modify the procedure to build RPMs that install into **/usr/local/games/crossfire**.
  
+ =====Optional: Setup .rpmmacros=====
  
- ====Set Up RPM Build Configuration====
- 
- ===.rpmmacros===
- 
- A key to building RPMs without using sudo or root is centered around creating a .rpmmacros file in the builder's home directory.  You only need a file like this set up if you want to build and install the rpm as a normal user.  To make RPMs that use distribution defaults, make sure that ~/.rpmmacros does not exist.
+ A key to building RPMs without using sudo or root is centered around creating a .rpmmacros file in the builder's home directory.  You only need a file like this set up if you want to build and install the rpm as a normal user.  To make RPMs that use distribution defaults, make sure that ~/.rpmmacros does not exist, or that it does not conflict with the system-wide settings.
  
    # /etc/rpm/macros # (c) GPL 2003 Tero.Karvinen at-sign iki.fi
    %packager %(echo "$USER")
    %_topdir /home/devel/crossfire/rpmbuild
@@ -334,12 +329,9 @@
    # Then you can build your rpm with
    #  rm -rf TMP/* BUILD/* ; rpmbuild -ba *.spec 2>&1 |tee rpmbuild.log
    # For more information, see www.iki.fi/karvinen
  
- 
- 
- 
- ====Set Up the Pre-Release Workspace====
+ =====Setup the Release Workspace=====
  
  Create the base workspace directory and make it your current working directory.
  
    $ export RELDIR=/home/devel/crossfire/rpmbuild
@@ -353,9 +345,9 @@
    $ wget http://invidious.meflin.net/~kbulgrien/files/trunk.config.sh
    $ wget http://invidious.meflin.net/~kbulgrien/files/branch.config.sh
    $ wget http://invidious.meflin.net/~kbulgrien/files/prerelease.sh
  
- =====Build Procedure=====
+ =====Create a Release or Snapshot=====
  
  It is only necessary to manually invoke the **prerelease.sh** script.  The other scripts are automatically called as needed.
  
  The built-in help for **prerelease.sh** shows:
@@ -385,15 +377,17 @@
    
      --maps-bz2
        Create a bzip2 maps tarball in addition to a gzip tarball.
  
- An example of how to build a release follows:
+ An example of how to build a snapshot release follows:
  
    $ bash prerelease.sh --trunk --client --name=First_I._Last --email=me at my.domain
  
    * If there are errors, rpmbuild will tell you.
    * RPMs will be put in RPM/RPMS/<architecture>
    * SRPM will be located in RPM/SRPMS
+ 
+ Making an official release is not yet fully implemented and tested, but the primary difference is adding a --release parameter to the **prerelease.sh** command-line.
  
  ======Bug Triage======
  
  =====crossfire-client-gtk2=====


IP-Address  : 68.90.128.197
Old Revision: http://wiki.metalforge.net/doku.php/user:kbulgrien?rev=1242292585
New Revision: http://wiki.metalforge.net/doku.php/user:kbulgrien

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