Fixes issue #2216 [Feature Request]

[baxtor]

"InstallShield setup.z extractor fails for Dune 2000"
Reverse engineered pascal code from "STIX", adjusted only a few line of code.
The blast implementation of OpenRA works perfectly with it.
Filename hashing should be removed 'cause of duplicate filenames in nested folders.

EDIT: please only merge "InstallShieldPackage.cs" I'm new to git. Maybe i'll create a concrete branch
for fixes.

[Mailaender]

Needs a git rebase see http://learn.github.com/p/rebasing.html and please send it towards https://github.com/OpenRA/OpenRA (bleed branch).

[baxtor]

Hi Matthias,

thanx for the info. To me it's a little bit messy with the tutorial video. I'd rebased my bleed branch and only want to push changes to that file to your top repo. Any quick guidelines to commit quickly without long book readings ?

Greetings
Andreas

Von meinem iPhone gesendet

Am 25.05.2013 um 12:23 schrieb Matthias Mailänder notifications@github.com:

Needs a git rebase see http://learn.github.com/p/rebasing.html and please send it towards https://github.com/OpenRA/OpenRA

—
Reply to this email directly or view it on GitHub.

[Mailaender]

We just merged a patch from @pchote which refactors the way the virtual filesystem works so you definitely have to fetch the latest openra/bleed branch and rebase your changes onto it.

git fetch openra assuming you called git@github.com:OpenRA/OpenRA.git that way
git checkout bleed your local bleed repository
git rebase -i openra/bleed gives you a little more control
There will be merge conflicts. Search for <<< and keep what you like / adapt your code.
git rebase --continue
git push+ origin bleed force push to overwrite history (non-fast-forward)

You might want to join #openra on FreeNode IRC for live help.

[baxtor]

I'll check that out. So console is already your best friend, thought that GUI clients can work this out ;).
Thanks for spending your time with me.

Best wishes
Andreas

Von meinem iPhone gesendet

Am 25.05.2013 um 14:41 schrieb Matthias Mailänder notifications@github.com:

We just merged a patch from @pchote which refactors the way the virtual filesystem works so you definitely have to fetch the latest openra/bleed branch and rebase your changes onto it.

git fetch openra assuming you called git@github.com:OpenRA/OpenRA.git that way
git checkout bleed your local bleed repository
git rebase -i openra/bleed gives you a little more control
There will be merge conflicts. Search for <<< and keep what you like / adapt your code.
git rebase --continue
git push+ origin bleed force push to overwrite history (non-fast-forward)

Click https://github.com/OpenRA/OpenRA/pull/new/bleed

—
Reply to this email directly or view it on GitHub.

[baxtor]

@Mailaender Yeah, think i've lost the thread o_O
git said that I'm successfully rebased the bleed. Am I up to date ?

[Mailaender]

Not sure, only @chrisforbes has access to this repository. Try an interactive rebase to clean up and then submit https://github.com/OpenRA/OpenRA/pulls so I can review it.

[Mailaender]

Superseded by OpenRA#3342