From Newsgroup: alt.os.linux


I installed HandBrake and HandBrake Video Converter on my new Linux installation.

HandBrake 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!

Is that a feature of Flatpak? Should it be avoided?
--
Jeff Gaines Dorset UK
The facts, although interesting, are irrelevant
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: alt.os.linux

Jeff Gaines wrote:

I installed HandBrake and HandBrake Video Converter on my new Linux >installation.

I am confused, you mention two installs, but there is just one
HandBrake.

HandBrake 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.

Is that a feature of Flatpak? Should it be avoided?

That is up to you: https://en.wikipedia.org/wiki/Flatpak

-jw-
--
And now for something completely different...
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: alt.os.linux

On 08/04/2024 in message <fof71jdl8s3ktih0rro9t760citpfc0s3m@joergwalther.my-fqdn.de> Joerg Walther wrote:

Jeff Gaines wrote:

I installed HandBrake and HandBrake Video Converter on my new Linux >>installation.

I am confused, you mention two installs, but there is just one
HandBrake.

HandBrake 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.

Is 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.
--
Jeff Gaines Dorset UK
You can't tell which way the train went by looking at the tracks
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: alt.os.linux

Jeff Gaines wrote:

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.

Most likely it's the same thing, once as a Flapak, once as a normal
package.

-jw-
--
And now for something completely different...
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: alt.os.linux

On 08/04/2024 12.03, Joerg Walther wrote:

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.

Not always true, can be for applications with a small dependency tree,
but just think of all the things GIMP and GPaint are depending on, it
would be quite big packages and you would need to download loads even if
the two programs share a lot of same dependencies. The maintainer has
also to keep track of vulnerabilities and bugs in all the dependencies
they need. so they tend to have dependencies to other flatpaks like
mesa, xorg and so on, to lessen the work they need to do. So a flatpak
you see listed and install may pull in a number of other flatpaks.

https://blogs.gnome.org/mclasen/2018/09/07/on-flatpak-dependencies/
--
//Aho
--- Synchronet 3.20a-Linux NewsLink 1.114

From Newsgroup: alt.os.linux

On 4/8/2024 6:13 AM, Jeff Gaines wrote:

On 08/04/2024 in message <fof71jdl8s3ktih0rro9t760citpfc0s3m@joergwalther.my-fqdn.de> Joerg Walther wrote:

Jeff Gaines wrote:

I installed HandBrake and HandBrake Video Converter on my new Linux
installation.

I am confused, you mention two installs, but there is just one
HandBrake.

HandBrake 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.

Is 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
--- Synchronet 3.20a-Linux NewsLink 1.114