alino74 wrote: ↑31 Aug 2022, 21:01
tried with vlc ....... creates the xzm, presents it in the menu..but it does not start ..... and if I copy it in the modules folder it loads it at boot, present in the menu but still does not start ...
When it does not start, most probably there are some dependencies missing.
Open a terminal and look where the binary to the program that fails to start sits.
Say, the binary is called vlc and it sits in /usr/bin - so that the full path to the binary is /usr/bin/vlc - the do this:
Code: Select all
ldd /usr/bin/vlc | grep "not found"
When there are libraries listed all these are missing.
Could be that when you create several modules for these libraries - or one larger module for all dependencies for your vlc in one singe module - after activating all these dependencies as well, you have to run
Code: Select all
ldd /usr/bin/vlc | grep "not found"
again, cause it could be that a now installed dependency needs yet another dependency that is also not installed yet.
I know, using usm was more easy, but the one who coded it was not able to do so any longer - it is a very complex program, like I explained above, sometimes dependencies need more dependencies, and from these 2nd level dependencies some need additional 3rd level dependencies…
But… usm had its downsides as well.
Say, a needed single library is not available as a package for the library itself but only as one file in a much larger package with dozens of other libraries and maybe even programs - then usm would suggest one or more packages that contain your needed library - but remember, you not really need any of these complete packages, for your one program you would only need the one single library (and its symlinks) - so usm often creates dependencies automatically that are much larger than you really need.
And that drives down the efficiency of Porteus. Automated tools are not always better than done manually by an expert (usually the expert is more efficient), but an automated tool is very helpful for a beginner.