Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Packaging issues #180

Open
jhonny-oliveira opened this issue Nov 29, 2020 · 1 comment
Open

Packaging issues #180

jhonny-oliveira opened this issue Nov 29, 2020 · 1 comment

Comments

@jhonny-oliveira
Copy link

jhonny-oliveira commented Nov 29, 2020

Hi!

I have recently packaged VDrift and published it here: https://launchpad.net/~xtradeb/+archive/ubuntu/play
I came across a couple of issues, such as the Python 2 dependency in the current official release (20141020), so I ended up creating a new "virtual" release with the latest code/data. Sorry for that!

I also came across a few other findings, please let me know the best way forward.

  • The game has its own metadata, Desktop file and icons:
    • usr/share/applications/vdrift.desktop
    • usr/share/metainfo/vdrift.appdata.xml
    • usr/share/games/vdrift/data/textures/icons/
      but
    • the desktop file cannot load the icon, due to its non standard location;
    • the metadata is in a very old format, so I create a quilt patch for the package;
    • the data (rev 1436) has an empty file "data/tracks/brands/.zip"
  • At the moment, the game binaries and data are not packaging/watch file friendly. Having a new release and download ready "zip"/txz files would be welcome.

Cheers!
Jhonny

Apteryks added a commit to Apteryks/vdrift that referenced this issue Oct 22, 2024
This fixes the icon not being found for XDG systems such as GNU/Linux,
partially addressing <VDrift#180>.
@Apteryks
Copy link
Contributor

@logzero I guess this empty file can be simply deleted: https://sourceforge.net/p/vdrift/code/HEAD/tree/vdrift-data/tracks/brands/.zip

Then this issue can be closed, I believe, unless you think the last point should be tackled, but I don't see a big problem with the status quo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants