From no-reply_wiki at metalforge.org Sat Apr 5 15:07:00 2014 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sat, 05 Apr 2014 15:07:00 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: crossfire_release_guide Message-ID: <1396728420.200932.22183.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/05 15:06 User : partmedia Edit Summary: Split up into logical sections @@ -1,19 +1,16 @@ + ====== Source Releases ====== + Directions below have 1.50.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.50.0 changes line to mark changes before/after the branch. Commit changed file: - - vi arch/branches/1.x/CHANGES - svn commit Changes - - * For maps, regenerate a new ChangeLog: + * Update and commit the ChangeLog (it may be called 'CHANGES'). This can be done automatically for the maps. - cd maps/trunk - svn2cl.sh + cd maps/trunk + svn2cl.sh * Make a copy of the repository. Note this does a copy on the server, so if your local copy is a out of sync, it won't matter. svn copy https://crossfire.svn.sourceforge.net/svnroot/crossfire/arch/trunk \ @@ -48,9 +45,9 @@ * If release notes for a file is needed, this appears to be done by uploading another file and noting it is a release note file * Release of arch is now done - === Client === + ===== Client ===== Start in branches/1.x * Update configure.ac with new version number * Update ChangeLog file, putting in break for new version @@ -116,22 +113,9 @@ * upload file to sourceforge, same steps, same type * Directions for upload in the arch and map apply for the client - === 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'' - * If there are errors, rpmbuild will tell you. - * Rpms would be put in _rpmdir/ - * Upload the RPMS, architecture is the architecture, type is rpm. - - === Server === + ===== Server ===== Start in server/trunk * Update ChangeLog file, putting in break for new version * Make a copy of the repository. Note this does a copy on the server, so if your local copy is a out of sync, it won't matter. @@ -184,9 +168,9 @@ rm -rf /tmp/test rm -rf /crossfire-1.50.0 - ==== Final Notes ==== + ===== 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.11.0 to 1.50.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. @@ -194,9 +178,24 @@ * At the top of the file, put in the notable changes - note you may already have these from the steps above. * At end of file, put in complete changelog file. * Send mail to crossfire-announce at lists.real-time.com. Note it is a moderated alias, so there may be some time lag in the message actually appearing. - === Windows specific things === + ====== Binary Releases ====== + + ===== 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'' + * If there are errors, rpmbuild will tell you. + * Rpms would be put in _rpmdir/ + * Upload the RPMS, architecture is the architecture, type is rpm. + + ===== Windows ===== See also [[crossfire_compile_guide#microsoft_c_windows]] for requirements. == Client == IP-Address : 108.78.191.158 Old Revision: http://wiki.metalforge.net/doku.php/crossfire_release_guide?rev=1332397157 New Revision: http://wiki.metalforge.net/doku.php/crossfire_release_guide -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sun Apr 27 19:01:32 2014 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sun, 27 Apr 2014 19:01:32 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: client_side_scripting:scripts:bash Message-ID: <1398643292.788455.29952.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/27 19:01 User : partmedia Edit Summary: Remove empty page @@ -1,4 +1 @@ - ==== Bash Scripts ==== - The scripts on this page or linked to from this page are working scripts that players have actually used. Feel free to contribute your own Bash script(s) here. If you do not have wiki edit access then send your script to (poof at eracc dot com) for consideration. - === The Scripts === IP-Address : 99.108.25.109 Old Revision: http://wiki.metalforge.net/doku.php/client_side_scripting:scripts:bash?rev=1155916136 New Revision: http://wiki.metalforge.net/doku.php/client_side_scripting:scripts:bash -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sun Apr 27 19:08:33 2014 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sun, 27 Apr 2014 19:08:33 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: client_side_scripting:scripts Message-ID: <1398643713.205418.29957.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/27 19:08 User : partmedia Edit Summary: Consolidate sample scripts on a single page @@ -1,10 +1,44 @@ - ==== Scripts ==== - [[client_side_scripting:scripts:bash|Bash Scripts]] + ====== Sample Scripts ====== - [[client_side_scripting:scripts:c|C/C++ Scripts]] + The sample scripts on this page are working programs contributed by players. Feel free to submit your own by posting it as an attachment to the Crossfire Discussion Mailing List. - [[client_side_scripting:scripts:perl|Perl Scripts]] + ===== C/C++ ===== - [[client_side_scripting:scripts:python|Python Scripts]] + *[[user:gxc:client_side_scripting:cplusplus-howto]] - HOWTO for using C++ scripts + *[[:user:gxc:scripts:food_watch]] -- Monitors your food and eats if it falls below a certain level. + *[[client_side_scripting:cfequip.cpp]] -- manages sets of equipment for different roles (fighting, spell casting, shopping :-)), docs. at top of file - [[client_side_scripting:scripts:tcl|Tcl Scripts]] + ===== Perl ===== + + * [[:user:mrbrklyn:scripts:pray]] -- Pray and Pray and Pray without a fishing weight on the keyboard + + * [[.perl:travel]] -- Walk from Euthville to Scorn. + + * [[:user:mhoram:scripts:level_up]] -- Reports which skills are nearing advancement. + + * [[:client_side_scripting:scripts:perl:travel]] -- Walks a player from one place to another. + + * [[:user:mhoram:scripts:watch_food]] -- Auto-applies food when you get hungry. + + * [[:user:mhoram:scripts:protect]] -- Casts an assortment of protection spells. + + * [[:user:mhoram:scripts:altar_pray]] -- Takes some of the tediousness out of praying at an altar. + + * [[:user:mhoram:scripts:healup]] -- Bring grace and hit points to maximum. + + * [[:user:mhoram:scripts:subs.pl]] -- Subroutines used by most of my other scripts. + + * [[:user:meflin:scripts:charge.pl]] -- Manage the charge/discharging of Power Crystals + + ===== Python ===== + + see [[user:katia:About Python]] if you are new to python. + + * [[client_side_scripting:book.py]] - A script that inscribes a book from a text file. (must have the "inscription" skill, along with something to write on) + * [[:user:eadmund:scripts:crossfire.py]] - A library of convenient functions for writing client scripts in Python (a rip-off of [[:user:mhoram:scripts:subs.pl]]) contributed by [[user:eadmund|Eadmund]] + * [[:user:eadmund:scripts:altar-pray]] - A port of [[user:mhoram:scripts:altar_pray]] to Python by [[user:eadmund|Eadmund]] + * [[user:katia:chatlog.py]] - A chat log for servers without Critical messages support. + + ===== Tcl ===== + + * [[:client_side_scripting:scripts:tcl:autopray]] -- Prays to max grace, including optional altar-spamming. * IP-Address : 99.108.25.109 Old Revision: http://wiki.metalforge.net/doku.php/client_side_scripting:scripts?rev=1220356828 New Revision: http://wiki.metalforge.net/doku.php/client_side_scripting:scripts -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sun Apr 27 19:09:05 2014 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sun, 27 Apr 2014 19:09:05 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: client_side_scripting:scripts:c Message-ID: <1398643745.336867.29969.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/27 19:09 User : partmedia Edit Summary: Consolidate sample scripts on a single page (remove) @@ -1,9 +1 @@ - ==== C Scripts ==== - The scripts on this page or linked to from this page are working scripts that players have actually used. Feel free to contribute your own C script(s) here. If you do not have wiki edit access then send your script to (poof at eracc dot com) for consideration. - - === The Scripts === - - *[[user:gxc:client_side_scripting:cplusplus-howto]] - HOWTO for using C++ scripts - *[[:user:gxc:scripts:food_watch]] -- Monitors your food and eats if it falls below a certain level. - *[[client_side_scripting:cfequip.cpp]] -- manages sets of equipment for different roles (fighting, spell casting, shopping :-)), docs. at top of file IP-Address : 99.108.25.109 Old Revision: http://wiki.metalforge.net/doku.php/client_side_scripting:scripts:c?rev=1241033231 New Revision: http://wiki.metalforge.net/doku.php/client_side_scripting:scripts:c -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sun Apr 27 19:09:15 2014 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sun, 27 Apr 2014 19:09:15 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: client_side_scripting:scripts:perl Message-ID: <1398643755.828943.29972.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/27 19:09 User : partmedia Edit Summary: Consolidate sample scripts on a single page (remove) @@ -1,24 +1 @@ - ==== Perl Scripts ==== - The scripts on this page or linked to from this page are working scripts that players have actually used. Feel free to contribute your own Perl script(s) here. If you do not have wiki edit access then send your script to (poof at eracc dot com) for consideration. - === The Scripts === - - * [[:user:mrbrklyn:scripts:pray]] -- Pray and Pray and Pray without a fishing weight on the keyboard - - * [[.perl:travel]] -- Walk from Euthville to Scorn. - - * [[:user:mhoram:scripts:level_up]] -- Reports which skills are nearing advancement. - - * [[:client_side_scripting:scripts:perl:travel]] -- Walks a player from one place to another. - - * [[:user:mhoram:scripts:watch_food]] -- Auto-applies food when you get hungry. - - * [[:user:mhoram:scripts:protect]] -- Casts an assortment of protection spells. - - * [[:user:mhoram:scripts:altar_pray]] -- Takes some of the tediousness out of praying at an altar. - - * [[:user:mhoram:scripts:healup]] -- Bring grace and hit points to maximum. - - * [[:user:mhoram:scripts:subs.pl]] -- Subroutines used by most of my other scripts. - - * [[:user:meflin:scripts:charge.pl]] -- Manage the charge/discharging of Power Crystals IP-Address : 99.108.25.109 Old Revision: http://wiki.metalforge.net/doku.php/client_side_scripting:scripts:perl?rev=1198519748 New Revision: http://wiki.metalforge.net/doku.php/client_side_scripting:scripts:perl -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sun Apr 27 19:09:25 2014 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sun, 27 Apr 2014 19:09:25 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: client_side_scripting:scripts:python Message-ID: <1398643765.519200.29975.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/27 19:09 User : partmedia Edit Summary: Consolidate sample scripts on a single page (remove) @@ -1,9 +1 @@ - ==== Python Scripts ==== - The scripts on this page or linked to from this page are working scripts that players have actually used. Feel free to contribute your own Python script(s) here. If you do not have wiki edit access then send your script to (poof at eracc dot com) for consideration. - see [[user:katia:About Python]] if you are new to python. - === The Scripts === - * [[client_side_scripting:book.py]] - A script that inscribes a book from a text file. (must have the "inscription" skill, along with something to write on) - * [[:user:eadmund:scripts:crossfire.py]] - A library of convenient functions for writing client scripts in Python (a rip-off of [[:user:mhoram:scripts:subs.pl]]) contributed by [[user:eadmund|Eadmund]] - * [[:user:eadmund:scripts:altar-pray]] - A port of [[user:mhoram:scripts:altar_pray]] to Python by [[user:eadmund|Eadmund]] - * [[user:katia:chatlog.py]] - A chat log for servers without Critical messages support. IP-Address : 99.108.25.109 Old Revision: http://wiki.metalforge.net/doku.php/client_side_scripting:scripts:python?rev=1349016968 New Revision: http://wiki.metalforge.net/doku.php/client_side_scripting:scripts:python -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sun Apr 27 19:09:33 2014 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sun, 27 Apr 2014 19:09:33 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: client_side_scripting:scripts:tcl Message-ID: <1398643773.196699.29978.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/27 19:09 User : partmedia Edit Summary: Consolidate sample scripts on a single page (remove) @@ -1,5 +1 @@ - ==== Tcl Scripts ==== - The scripts on this page or linked to from this page are working scripts that players have actually used. Feel free to contribute your own Tcl script(s) here. If you do not have wiki edit access then send your script to (poof at eracc dot com) for consideration. - === The Scripts === - * [[:client_side_scripting:scripts:tcl:autopray]] -- Prays to max grace, including optional altar-spamming. * IP-Address : 99.108.25.109 Old Revision: http://wiki.metalforge.net/doku.php/client_side_scripting:scripts:tcl?rev=1220357207 New Revision: http://wiki.metalforge.net/doku.php/client_side_scripting:scripts:tcl -- This mail was generated by DokuWiki at http://wiki.metalforge.net/ From no-reply_wiki at metalforge.org Sun Apr 27 19:17:52 2014 From: no-reply_wiki at metalforge.org (no-reply_wiki at metalforge.org) Date: Sun, 27 Apr 2014 19:17:52 -0500 Subject: [Crossfire-wiki] [Crossfire DokuWiki] page changed: client_side_scripting:scripts Message-ID: <1398644272.756553.29989.nullmailer@metalforge.net> A page in your DokuWiki was added or changed. Here are the details: Date : 2014/04/27 19:17 User : partmedia Edit Summary: Remove (broken) duplicate link @@ -10,10 +10,8 @@ ===== Perl ===== * [[:user:mrbrklyn:scripts:pray]] -- Pray and Pray and Pray without a fishing weight on the keyboard - - * [[.perl:travel]] -- Walk from Euthville to Scorn. * [[:user:mhoram:scripts:level_up]] -- Reports which skills are nearing advancement. * [[:client_side_scripting:scripts:perl:travel]] -- Walks a player from one place to another. IP-Address : 99.108.25.109 Old Revision: http://wiki.metalforge.net/doku.php/client_side_scripting:scripts?rev=1398643709 New Revision: http://wiki.metalforge.net/doku.php/client_side_scripting:scripts -- This mail was generated by DokuWiki at http://wiki.metalforge.net/