Closed GoogleCodeExporter closed 9 years ago
This means you don't have any tracks and/or cars.
Original comment by scrawl...@gmail.com
on 8 Apr 2011 at 11:40
Original comment by scrawl...@gmail.com
on 8 Apr 2011 at 11:41
Of course, we could handle this more gracefully and spit out an appropriate
error that no cars or tracks were found, and quit.
Original comment by scrawl...@gmail.com
on 8 Apr 2011 at 11:47
I have included the packages with data and tracks. Where exactly they should be
located? I have currently the following structure:
/usr/share/stuntrally/cars
/usr/share/stuntrally/tracks
/usr/share/stuntrally/materials
/usr/share/stuntrally/hud
/usr/share/stuntrally/terrain
etc.
Original comment by neptu...@mail.ru
on 8 Apr 2011 at 12:41
The location is correct. So there is actually content in cars and tracks?
Original comment by scrawl...@gmail.com
on 8 Apr 2011 at 12:47
Well seems all the files in /tracks are not permitted for reading. This is
because 7zip archiver is used that does not preserve privileges.
Original comment by neptu...@mail.ru
on 8 Apr 2011 at 1:46
I suggest to use .tar.bz2 everywhere. This would allow to unpack the files with
standard setup script. Currently I have to use "7z x" command in the spec file
and copy the contents into the proper place manually. The build service also
throws a warning if the sources are not in .tar.bz2 format and such packages
are not accepted to the core repository.
Original comment by neptu...@mail.ru
on 8 Apr 2011 at 1:59
Using 7z also requires additional build dependency on p7zip.
Original comment by neptu...@mail.ru
on 8 Apr 2011 at 2:02
Ok, we have tar.bz2 for data and source too, so this shouldnt be a problem.
Original comment by scrawl...@gmail.com
on 8 Apr 2011 at 2:57
My proposal for archives uploaded with next release (and subsequent ones) can
be read from the ReleaseProcess wiki page. In a nutshell, I propose the source
archive contains all data and tracks, and is in .tar.bz2 format.
Original comment by tapiovie...@gmail.com
on 9 Apr 2011 at 12:01
I second that. Then you could download everything needed in 1 file.
Original comment by scrawl...@gmail.com
on 9 Apr 2011 at 12:06
By the way, cmake does not install tracks directory automatically even if it is
present.
Original comment by neptu...@mail.ru
on 9 Apr 2011 at 2:47
In my system, they are installed fine. Did you put the tracks-dir inside the
data dir? There should also be a warning "WARNING: No tracks could be found for
installation." if the tracks are not in the right place.
Original comment by tapiovie...@gmail.com
on 9 Apr 2011 at 3:38
> Did you put the tracks-dir inside the data dir?
Yes.
> "WARNING: No tracks could be found for installation."
No warning. This is the build log:
https://build.opensuse.org/package/rawlog?arch=x86_64&package=StuntRally&project
=home%3AAnsus%3Agames&repository=games_openSUSE_11.4
Original comment by neptu...@mail.ru
on 9 Apr 2011 at 3:43
The only warning is
CMake Warning (dev) at data/CMakeLists.txt:9 (add_subdirectory):
The source directory
/usr/src/packages/BUILD/StuntRally/data/tracks
does not contain a CMakeLists.txt file.
CMake does not support this case but it used to work accidentally and is
being allowed for compatibility.
Original comment by neptu...@mail.ru
on 9 Apr 2011 at 3:45
"""
CMake Warning (dev) at data/CMakeLists.txt:9 (add_subdirectory):
The source directory
/usr/src/packages/BUILD/StuntRally/data/tracks
does not contain a CMakeLists.txt file.
"""
The CMakeLists.txt is missing. For now it needs to be obtained from hg (or
included in as package patch or something, it's only a couple of lines). This
will be addressed in the next release, with new archives.
I don't know how the build service and openSUSE packaging work, but if it's
possible, it might be easiest to just pull sources and data straight from the
mercurial and use tags to get specific release.
Original comment by tapiovie...@gmail.com
on 9 Apr 2011 at 3:57
> I don't know how the build service and openSUSE packaging work, but if it's
possible, it might be easiest to just pull sources and data straight from the
mercurial and use tags to get specific release.
Possibly. As I know, such possibility exists.
Original comment by neptu...@mail.ru
on 9 Apr 2011 at 4:04
Closing, since the original issue is fixed.
Original comment by scrawl...@gmail.com
on 11 Apr 2011 at 4:24
Original issue reported on code.google.com by
neptu...@mail.ru
on 8 Apr 2011 at 10:16Attachments: