Post by Joerg WaltherPost by Jeff GainesI installed HandBrake and HandBrake Video Converter on my new Linux
installation.
I am confused, you mention two installs, but there is just one
HandBrake.
Post by Jeff GainesHandBrake was a "System" install and asked for authorisation once. The
Video Converter had a heap of dependencies and was a Flatpak install -
which asked for separate authorisation for each library and each change of
depository!
Your information is quite contradictory. A Flatpak is a program install
which includes the main program and all dependencies in one big packet
which runs in its own kind of sandbox. You have to authorise this only
once. It sounds like you also installed a second version of handbrake,
not a Flatpak, which of course, being a video converter, comes with all
kinds of dependencies, which you authorised.
Post by Jeff GainesIs that a feature of Flatpak? Should it be avoided?
That is up to you: https://en.wikipedia.org/wiki/Flatpak
-jw-
The second program is called "HandBrake Transcoder" which says it can convert between different formats and was only available as a Flatpak. I installed HandBrake first then the transcoder once HandBrake install was complete so all the authorisations definitely arose from the Transcoder install.
Are you executing a command to invoke flatpaks specifically ?
If you're using "sudo synaptic", the handbrake in there is
a pair of .deb, one is "handbrake" and one is "handbrake-cli"
for command line invocation.
Synaptic on Ubuntu has Debian .deb installs and it can
invoke "snap install something" as a second means of
achieving a result. If you want flatpak or appimage,
then those steps can probably be managed, but there
would be a different recipe/ceremony for that and
at least partially outside the confines of the tree.
Programs use libraries, and the libraries need to be
installed if they are not currently resident.
If you have a web page for the recipe/ceremony you
carried out, post the URL for comment.
Paul