Difference between revisions of "GRFPack Dev Guide"
From #openttdcoop wiki
(→Release) |
(Revert a commit) |
||
Line 44: | Line 44: | ||
move it to [[GRF Table Removed]] and give a reason... | move it to [[GRF Table Removed]] and give a reason... | ||
The GRF itself needs to be moved to z_obsolete. (save compatibility) | The GRF itself needs to be moved to z_obsolete. (save compatibility) | ||
+ | |||
+ | == Revert a commit == | ||
+ | change to the directory where the GRF is, then | ||
+ | |||
+ | '''svn export -r <revision to revert -1> ./ ./ --force''' | ||
+ | |||
+ | commit the change... | ||
==Preambles for SVN commits== | ==Preambles for SVN commits== |
Revision as of 17:35, 3 June 2008
Quick Howto:
- Checkout or Update trunk: svn co https://svn.openttdcoop.org/grfpack/trunk ottdc_grfpack_trunk or cd ottdc_grfpack_trunk && svn up
- Download the GRF to the right place
- Open the GRF in OpenTTD
- Commit the GRF to REPO: svn ci -m "New/Update: ...."
- Edit the GRF_Table_(Trunk)
- done
This is a guide to update our #openttdcoop NewGrf Package with Subversion and documenting the changes in GRF Table (Trunk).
- GRFs in alpha/beta state does change many times and should be checked before releasing new pack.
- The data from a GRF could be differ then the data from the webpage or forum or whatever, I would suggest to take the data from the GRF.
- GRFCrawler isn't always "right", TT-Forums should work if no official link available, links mostly change after update there...
- loading the GRF in OpenTTD might be a good idea for checking title, credits etc. (Title in GRF Table should be the same...)
- if there is a readme available, a link from column Details would be nice (link to www.openttdcoop.org/newgrfs/...)
Updating existing NewGRF
- Double check if it is really an update (md5sum)
- Commit to SVN with a proper message (svn commit)
- Update GRF Table (Trunk)
- Edit title and version number.
- Check the link to the grf authors page (still correct after version update, avoid 404!)
- After updates, the credits might also change...
- Write the svn revision (of our grfpack) into the status column
Adding new GRF
- Create a directory in the category, the NewGrf belongs to. Possibly the NewGrf needs another location because of a special dependency. Then you create a folder with a prefix (i.e. "a_") or you move it to the top directory (1_others) or to bottom (9_last). EVERY GRF has its own directory. (svn add <grffolder>)
- Update GRF Table (Trunk)
- Title with version number
- Link to grf
- Don't forget the credits (you see them in the GRF itself...)
- Write the svn revision (of our grfpack) into the status column
Deleting a GRF
move it to GRF Table Removed and give a reason... The GRF itself needs to be moved to z_obsolete. (save compatibility)
Revert a commit
change to the directory where the GRF is, then
svn export -r <revision to revert -1> ./ ./ --force
commit the change...
Preambles for SVN commits
- Update: Updating an existing NewGrf
- New: Adding a new NewGrf
- Orders: Moving an existing NewGrf to another location to fix order dependencies
- Fix: Fixing some other bugs ;-)
- Remove: Deleting an existing NewGRF (with reason)
- Release: Creating a new tag in /grfpack/tags
Release
- Creating wiki branch (copy GRF Table (Trunk) to GRF Table $VERSION) Download GRF Table to trunk with httrack i.e.
- Updating Readme
- Updating ottdc_grfpack.cfg (Script makenewgrfcfg)
- Tagging
- Generate the release packages.(Script eportpacks (editing config first ;-)
- Generating md4sum list: http://www.openttdcoop.org/newgrfs/ottdc_grfpack.md5sum