0.11.1 Release

Everything about development and the OpenMW source code.
safferli
Posts: 14
Joined: 06 Aug 2011, 23:06

Re: 0.11.1 Release

Post by safferli » 03 Oct 2011, 12:27

BrotherBrick wrote:As an ex-Gentoo dev, I'll leave the ebuild an excercise to remaining devs. ;)
Oh no, please don't! :) There are far more gentoo users than devs ;)

User avatar
psi29a
Posts: 4718
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: 0.11.1 Release

Post by psi29a » 12 Oct 2011, 11:52

Gentlemen,

I've updated the packages once again and this built against Ubuntu 11.10 (Oneric Ocelot). I've also adjusted the CMakeList.txt file accordingly, I tried pushing to git but got this error message:
brick:~/workspace/openmw$ git push
fatal: remote error:
You can't push to git://github.com/zinnschlag/openmw.git
Use [email protected]:zinnschlag/openmw.git
Once commited, what else needs to be done? I've experience in cvs, svn and mercurial... first time git user. ;)

The only package that you will not be able to find in Ubuntu itself but can found here:
http://dk.archive.ubuntu.com/getdeb/ubu ... _amd64.deb
http://dk.archive.ubuntu.com/getdeb/ubu ... 1_i386.deb

The openMW packages are here:
http://dl.dropbox.com/u/396161/openmw_0.11.1_amd64.deb
http://dl.dropbox.com/u/396161/openmw_0.11.1_amd64.rpm
http://dl.dropbox.com/u/396161/openmw_0 ... d64.tar.gz
http://dl.dropbox.com/u/396161/openmw_0.11.1_i386.deb
http://dl.dropbox.com/u/396161/openmw_0.11.1_i386.rpm
http://dl.dropbox.com/u/396161/openmw_0 ... 386.tar.gz

Enjoy

User avatar
Zini
Posts: 5537
Joined: 06 Aug 2011, 15:16

Re: 0.11.1 Release

Post by Zini » 12 Oct 2011, 12:42

You need to fork the repo on github, create a local clone of the fork, commit changes to this clone, push to the fork and then send a pull request.

Github has useful documentation on this topic.

User avatar
psi29a
Posts: 4718
Joined: 29 Sep 2011, 10:13
Location: Belgium
Gitlab profile: https://gitlab.com/psi29a/
Contact:

Re: 0.11.1 Release

Post by psi29a » 12 Oct 2011, 13:02

Zini wrote:You need to fork the repo on github, create a local clone of the fork, commit changes to this clone, push to the fork and then send a pull request.

Github has useful documentation on this topic.
Crash course completed... pull request sent! :)

User avatar
raevol
Posts: 3054
Joined: 07 Aug 2011, 01:12
Location: Caldera

Re: 0.11.1 Release

Post by raevol » 12 Oct 2011, 17:46

I'll try to test when I get home, but if someone can take these for a spin before I get to, I should be able to upload them from work.

User avatar
raevol
Posts: 3054
Joined: 07 Aug 2011, 01:12
Location: Caldera

Re: 0.11.1 Release

Post by raevol » 24 Oct 2011, 08:02

Resurrecting this thread because I and apparently everyone else forgot about it. :( The libbullet package is giving me a 404 now. :(


User avatar
raevol
Posts: 3054
Joined: 07 Aug 2011, 01:12
Location: Caldera

Re: 0.11.1 Release

Post by raevol » 24 Oct 2011, 10:05

Those worked for me! I have the launcher running! I am trying to figure out how to configure my data dir! This is so exciting!

User avatar
raevol
Posts: 3054
Joined: 07 Aug 2011, 01:12
Location: Caldera

Re: 0.11.1 Release

Post by raevol » 24 Oct 2011, 10:12

omg it works *dies*

Ok so if we can get these .deb builds automated and pushed to me regularly I can do all kinds of QA. :) For now, should I upload the packages to the google code page? What do we want to do about the libbullet dependency?

User avatar
Zini
Posts: 5537
Joined: 06 Aug 2011, 15:16

Re: 0.11.1 Release

Post by Zini » 24 Oct 2011, 15:31

should I upload the packages to the google code page?
Yes, please.
What do we want to do about the libbullet dependency?
Those alternative links work, don't they?

Post Reply