We'll receive bug reports, as usual, and if the reported issues with fglrx can be worked around we'll be releasing maintenance versions as r2, r3 and so on.
We're using OpenSUSE's Build Service (OBS for short), and the packages are there already, so if you installed from OBS you should be able to update rather easily (hopefully, even with delta rpms ) - not all repos have been tested, so if you're on one of the unlucky ones to spot a packaging bug, please post on the bug tracker ASAP.
vegastrike-music and vegastrike-speech were unchanged so you don't have to update. "Updated" versions are there since r1 is the first official (non-beta) release.
Linux
You can look for the packages in OBS' search interface, or you can set up the repos from the urls below (which is the best way to get updates):
For the most popular linux distros (available in OBS), we have zypper/deb repos:
- OpenSUSE 11.1
- OpenSUSE 11.4 - (instructions)
- OpenSUSE 12.1 - (instructions)
- OpenSUSE 12.2 - (instructions)
- OpenSUSE Factory - (instructions)
- Fedora 15 (discontinued)
- Fedora 16 - instructions
- Mandriva 2009.1 (x86_64 broken atm - but you can try i586) - instructions
- Mandriva 2010.1 (x86_64 broken atm - but you can try i586) - instructions
- Mandriva 2010 (x86_64 broken atm - but you can try i586) - instructions
- Debian 5.0] (lenny) - (discontinued)
- Debian 6.0 (squeeze) - instructions
- Debian 7.0 (wheezy) - instructions
- Ubuntu 9.04 (jaunty) - (discontinued)
- Ubuntu 9.10 (karmic) - (discontinued)
- Ubuntu 10.04 (lucid) - instructions
- Ubuntu 10.10 (maverick) - instructions
- Ubuntu 11.04 (natty) - instructions
- Ubuntu 11.10 (oneiric) - instructions
- Ubuntu 12.04 (precise) - instructions
- Ubuntu 12.10 (precise) - instructions
- Ubuntu 13.04 (precise) - instructions
Most RPM-based distros use yum or yum-compatible tools, so you just have to download the repo description into the proper path: "sudo wget {repository path}/{repo name}.repo -O /etc/yum.repos.d/{repo name}.repo" (for openSuse, it's /etc/zypp/repos.d). You'll probably have to browse the repository to find the "repo name" (it's not evident from the above links, derived from OBS project settings).
It should prompt whether to import the repo key next time you update metadata, with zypper refresh or yum update.
Other distros
If your distro is not on the list, source tar balls and data packages can be downloaded directly from sourceforge:
Instructions for building from source and installing data from the tarballs in your home folder would go like this, assuming you've downloaded the pertinent tarballs and dependencies already:
Code: Select all
~$ mkdir vegastrike-0.5.1.r1
~$ tar xvjf vegastrike-src-0.5.1.r1.tar.bz2
~$ cd vegastrike-src-0.5.1.r1
~/vegastrike-src-0.5.1.r1$ mkdir build
~/vegastrike-src-0.5.1.r1$ cd build
~/vegastrike-src-0.5.1.r1/build$ cmake ..
...
~/vegastrike-src-0.5.1.r1/build$ make
...
~/vegastrike-src-0.5.1.r1/build$ cd ../../vegastrike-0.5.1.r1
~/vegastrike-0.5.1.r1$ mkdir bin
~/vegastrike-0.5.1.r1$ cp ../vegastrike-src-0.5.1.r1/build/{vegastrike,vegaserver,setup/vssetup,objconv/mesh_tool} bin/.
~/vegastrike-0.5.1.r1$ tar xvjf ../vegastrike-data-0.5.1.r1.tar.bz2 --strip-components=1
...
~/vegastrike-0.5.1.r1$ tar xvjf ../vegastrike-extra-0.5.1.r1.tar.bz2 --strip-components=1
...
~/vegastrike-0.5.1.r1$ tar xvf ../vegastrike-music-0.5.1.r1.tar --strip-components=1
...
~/vegastrike-0.5.1.r1$ tar xvf ../vegastrike-speech-0.5.1.r1.tar --strip-components=1
...
Windows
Windows is up and ready. You can download from SourceForge download area.
Bug reports
Many distros (not all) have a vegastrike-debuginfo or vegastrike-dbg package you can use to install debugging info and provide better stacktraces for bug reporting - please, when reporting a crash-type bug, install that package and run vegastrike through gdb:
Code: Select all
$ gdb --args vegastrike --debug=3 2>stderr.txt
(gdb) run
...
Segmentation Fault
(gdb) bt full
<paste this in your bug report>