I improved my post so that the contents of the files can be seen better.
I’m trying to use the commands suggested by the fedora documentation which are not the classic flatpak-builder, but for example flatpak-module, which should allow you to directly enter the use of rpm(s) for the libraries to be added.
Yeah, i’m sorry but I have not had to build packages under the new style. all my experience is with the old way ( shouldn’t be too different? ). I don’t have the environment to build and test this for you.
You have no reason to be sorry, I’m the one who tried to follow a path that theoretically should be easy, convenient and automatic (it seems to me that fedora uses it to automatically transform RMP(S) into flakpack).
The problem is my total inexperience and my groping here and there.
Things are starting to work, I’m missing some dependencies and then testing if the program installed by flatpak works (which I doubt).
This is my current manifest (if you, or anyone else, have any advice or criticism, thank you)
It is quite a classic of the programmers, especially in open source, perhaps there is a lot of documentation of the individual and specific parts, but documentation that explains how to do things is little and contradictory.
Now comes the really difficult part, lm_sensors and hddtemp don’t work properly, they don’t see the hardware and probably their configuration files.
And maybe this is another dead end.
I could use the help of someone experienced in this part, but I doubt that will happen.
Can you post your current Manifest ? .yaml files and build commands (flatpak-build etc…)
something like :
modules:
- name: ksensors
# ... other configurations
permissions:
- path: /dev/bus/usb/* # Example for USB sensors
mode: access user
- path: /dev/i2c* # Example for I2C sensors (adjust paths as needed)
mode: access user
Also just from thought you might need to provide --filesystem=host is there are any configuration files it needs to access.
I suspect that I will have to customize the programs so that they behave differently within the flatpak package.
P.S. I have to say that flatpak is quite fascinating, what it manages to do, given the enormous complexities it has to deal with, is a discreet miracle.
You’re probably right, I need to do some experimenting and learn how to set access permissions.
it’s a good opportunity to learn almost about debugging a flatpak package.
The initial insistence on trying to use the fedora style build was also for the purpose of learning and gathering information, by banging my head against that wall I learned almost everything I know (very little ).
Try including hddtemp.db within your flatpak by adding the directory containing the file to the sources section of the hddtemp module in your ksensors5.yaml
Under the modules section, consider adding a permissions section to grant access to the required device files.
I’m a little bit stretched here, but I’ll give you all I can to help. It’s been far too long since I built Flatpaks.
I’m a little bit stretched here, but I’ll give you all I can to help. It’s been far too long since I built Flatpaks.
Please don’t stress yourself more about this.
The help given is already good, if this doesn’t amuse you, if it weighs on you, forget it, take care of yourself and the things around you.
Hmm, Well keep us posted and let’s see how far we can get.
It’s no problem. The only issue is that I don’t have my main machine accessible at the moment. There, I would have easily recreated it and helped more. I also have a lot of my old flatpak builds and tools.
Here is a Manifest from a project that also uses sensors etc, maybe contrast and compare?
Also try : flatpak run --command=bash <app>
You’ve already attempted to copy it during the build process, but encountered a read-only filesystem issue.
Instead of trying to copy it directly to /usr/share/misc/, you can place the hddtemp.db file in a directory within your Flatpak application’s sandbox during the build process. Then, ensure that hddtemp knows where to find it.
From what I understand and read, I still have a lot to learn, it will take me a while.
It seems that programs launched by kensors5 do not have the access privileges assigned to ksensors5, you need to modify it so that it launches commands using for example flapak-spawn.
Then I want to avoid double databases, settings and configurations, of the hardware description (in the host and in the flatpak package).
). I don’t have the environment to build and test this for you.
).