About JohannesA

CodeShepherd · ‎10-10-2022

In my post above I mentioned the paths where the settings.js file is expected. After installation it is only in the installation path available and can be put to the active configuration to be "replaced". Also as mentioned above: You should copy out an original Settings.js already prepared by us for normal usage (otherwise the snap will/could stop working) from the third path, then add your extensions and load it to e.g. the first path to be persistent.

JohannesA · ‎04-08-2022

Hi maybe you are looking for "stage-packages" ? If you have to add own libraries you can dump it into the snap using the dump plugin. $SNAP/lib:$SNAP/usr/lib:$SNAP/usr/lib/x86_64-linux-gnu (on amd64 architecture) are default part of the LD_LIBRARY_PATH If you add your library to another directory within your snap you have to extend the environment variable e.g.: apps: example-app: [...] environment: LD_LIBRARY_PATH: $LD_LIBRARY_PATH:$SNAP/<example-directory> Regards Johannes

JohannesA · ‎06-24-2021

Hi Maurus, regarding the version number there is no dependency and no relation between those two files. The version of the package-manifest.json is used to retain backwards compatibility in case of format changes. Currently there is only version 1.0.0 Best Regards Johannes

JohannesA · ‎06-24-2021

Hi Maurus, regarding the version number there is no dependency and no relation between those two files. The version of the package-manifest.json is used to retain backwards compatibility in case of format changes. Currently there is only version 1.0.0 Best Regards Johannes

MauroRiboniMX · ‎06-16-2021

HI jochen-scheib, really cool!!

About JohannesA

Re: Option to replace the Settings.js file from the NodeRed snap

Re: SNAP how to use dynamic linker ldconfig or LD_LIBRARY_PATH

Re: Snap Version snapcraft.yaml vs package-manifest.json

Re: Snap Version snapcraft.yaml vs package-manifest.json

Re: SDK 1.8.0 Python example