DBP repository


I found that when I didn't have write access on an SD card it was when I inserted the card into a different pc and didn't remove it safely. I have never seen this behavior on a different device but purposely safely removing/ejecting the card always made it work.
 
Hi, I have a question regarding dependencies.

So if we have deb dependencies but debian is annoying because the difference between buster and bookworm can be a good major let alone minor version number. How do we handle that in the desktop file? A good example is LUA, on the CorsixTH dbp, it would be liblua5.4 on bookworm, but buster is lua5.3 and I feel the system doesnt handle just having "liblua" (where the version string wouldn't matter)

Is there a nice way to handle this? I find this part very useful for people with dbps with weird dependencies they might not have installed.
 
Not sure if I understand your problem correctly, but when a program needs a specific version of a library, I just include the required libraries directly in my program and assign the path with LD_LIBRARY_PATH.
 
This is the dependency line in the desktop file for a dbp. I know they're not automatically installed at this time, but great way to inform someone of dependency changes.

Problem is, if i set them for buster and you run the dbp on bookworm, they'll never be satisified so will always get a warning on running the file.
 
Luckily it's not that often a specific version of a library is needed. So most cases, a dbp compiled on buster would run fine on bookworm.
I had a similar problem with CaveExpress on buster where liblua 5.2 was needed.
So in these rare cases i think it's still the best solution to include the libraries locally unless someone has an idea how to distinguish the debian version in the dbp's desktop file!
 
including the libraries in the pnd is a handy, good idea. Not at that level just yet but could see how useful that is. Good idea cheers
 
Link errors are quite common in my (limited) dbp experience. And dependencies on unavailable pkg versions. And odd bugs presumably due to changes in dependency behavior. Was thinking something like AppImage might be nice.
 
Back
Top