tauri-apps/tauri

[bug] RPM installer places resources in wrong path

livwvil opened this issue · 1 comments

Describe the bug

DEB and MSI correctly place resources in the system, but RPM does not.
It seems that the configuration (bundle -> resources) for generating RPM is used incorrectly.

Before running the build command, I place my resources next to tauri.conf.json in the res folder.

My config:

    "resources": {
      "res/resources/first.db": "resources/first.db",
      "res/resources/second.bin": "resources/second.bin",
      "res/resources/third.db": "resources/third.db",
      "res/resources/fourth.db": "resources/fourth.db"
    },

I want the installer to place my resources in the same way that almost all installers do:

  • <res-base>/resources/first.db
  • <res-base>/resources/second.bin
  • <res-base>/resources/third.db
  • <res-base>/resources/fourth.db

But RPM does like that:

  • <res-base>/res/resources/first.db
  • <res-base>/res/resources/second.bin
  • <res-base>/res/resources/third.db
  • <res-base>/res/resources/fourth.db

After installing such RPM I get a non-working application.
As a bonus here we see that the resource directories differ even without installing:

image

Reproduction

  1. Clone repo https://github.com/livwvil/tauri2-rpm-build-problem
  2. Switch to the resources-problem branch
  3. Use build:image and build:container commands to produce bundles

Expected behavior

No response

Full tauri info output

All correct

Stack trace

No response

Additional context

No response

Please fix it in tauri v1 too