yolinlin/mod-ale
1
0
Fork 0
mirror of https://github.com/azerothcore/mod-ale synced 2025-11-29 15:38:17 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update INSTALL.md

Browse Source
This commit is contained in:
Rochet2
2014-03-27 10:59:06 +02:00
committed by Foereaper
parent a8a57f8530
commit f31561ea3e
1 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/INSTALL.md
View File

@@ -9,8 +9,7 @@
2. Open `git bash` and do 2. Open `git bash` and do
`git submodule init` `git submodule init`
`git submodule update` `git submodule update`
5. additionally to get latest Eluna code you can do `git submodule foreach git pull origin master` 3. Compile the core normally (use cmake if needed)
6. Compile the core normally (use cmake if needed)
#Updating #Updating
1. When updating you should take up the `commit hash` you are on, just in case. 1. When updating you should take up the `commit hash` you are on, just in case.
@@ -18,10 +17,9 @@ You can get it from git with `git log` for example.
You should take note what are the newest SQL updates in `sql/updates/*` folders. You should take note what are the newest SQL updates in `sql/updates/*` folders.
2. Use `git pull` to get the newest source changes. 2. Use `git pull` to get the newest source changes.
3. Then use `git submodule init` `git submodule update` to update Eluna from github. 3. Then use `git submodule init` `git submodule update` to update Eluna from github.
4. additionally to get latest Eluna code you can do `git submodule foreach git pull origin master` 4. Try compiling and if you encounter errors, report to [support](https://github.com/ElunaLuaEngine/Eluna#links) or [issues](https://github.com/ElunaLuaEngine/Eluna/issues).
5. Try compiling and if you encounter errors, report to [support](https://github.com/ElunaLuaEngine/Eluna#links) or [issues](https://github.com/ElunaLuaEngine/Eluna/issues).
You can revert back to the old sources by using `git reset --hard 000000` `git submodule update`, where 000000 is the `commit hash`. You can revert back to the old sources by using `git reset --hard 000000` `git submodule update`, where 000000 is the `commit hash`.
6. If the compiling was successful, you should update your database if needed. 5. If the compiling was successful, you should update your database if needed.
You can do this by running all **new** SQL files in `sql/updates/*`. You can do this by running all **new** SQL files in `sql/updates/*`.
You need to see your notes from before pulling the updates or you can use the old commit hash to see on github what were the last files you ran. You need to see your notes from before pulling the updates or you can use the old commit hash to see on github what were the last files you ran.
An easy way is to just look at the created/modified date on the files. An easy way is to just look at the created/modified date on the files.