home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   alt.os.linux.ubuntu      I preferred Xubuntu, seemed a bit faster      134,477 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 133,059 of 134,477   
   Mike Easter to Bobbie Sellers   
   Re: KDE Neon vs Snap   
   27 Oct 22 11:48:20   
   
   From: MikeE@ster.invalid   
      
   Bobbie Sellers wrote:   
   > Mike Easter wrote:   
   >> Henry Crun wrote:   
   >>> Mike Easter wrote:   
   >>>> Another Ub derivative goes its own way vs Snap.   
   >>>>   
   >>>> KDE Neon 221023 based on Ub 22.04 & KDE 5.26.1 departs Ub's big idea   
   >>>> of Snap and such as Snap Firefox.   
   >>>>   
   >>>> It says:   
   >>>>   
   >>>> snap list   
   >>>> no snaps are installed   
   >>>>   
   >>>> It also says that its repo/s include the mozillateam .ppa for its   
   >>>> Ffx 106.0.1, which repo also contains Tb 102.4 .deb.   
   >>>>   
   >>>> Neon does have an operative Flatpak/flathub.   
   >>>   
   >>> the difference is:   
   >>>   
   >>> $ snap list   
   >>>   
   >>> Command 'snap' not found, but can be installed with:   
   >>> sudo apt install snapd   
   >>>   
   >> Yes, you are correct; snapd is installed in the live default.   
   >>   
   >> The default Discover Settings shows flatpak checked, firmware updates   
   >> only linux vendor firmware service checked, snap appears to be   
   >> 'checked' but it is not blue color check like flatpak and the KDE Neon   
   >> repo/s which are also designated default.   
   >>   
   >> I'm not sure I completely understand how to interpret the Discover   
   >> settings graphical 'meaning'.   
   >>   
   >> The Discover 'treatment' of options for flatpak are distinctly   
   >> different from its graphical treatment of snap, firmware updates, and   
   >> kde neon repo/s.  Not only does flatpak have a function to make   
   >> default and add source, but it also has a trashcan to remove it.   
   >>   
   >> I don't see a function in Discover to remove snap; so apparently   
   >> Discover handles its Snap function differently than it does its   
   >> flatpak function.   
   >>   
   >> Puzzling.   
   >>   
   >      Sorry to hear that the updates have gotten so weird.   
   >      Don't care for the concepts in Flatpaks or in Snaps but   
   > then after paying for yearly or bi yearly updates to Mandriva   
   > for 5 years then to be left without help and a computer that   
   > was very unhappy with 2011.  Probably why I prefer a sturdy   
   > Rolling Relase and am now using Linux 6.0.5 & KDE 5.26.2.   
   > Delivered via apt-rpm via Synaptic.   
   >   
   > The thill of a working new kernel and getting my Usenet   
   > connection back after a glitch at the server is like   
   > a taste of my youth.   
   >   
   I don't run any rolling releases as rolling; whenever I boot a 'roller'   
   type distro, it is always just as a live USB, so I don't have good or   
   bad experiences w/ rollers updating/upgrading.  I do keep up w/ the   
   write-ups of the good and bad of rollers by such as the review Jesse   
   Smith did a few years ago comparing several w/ their individual tendency   
   to breakage or not on update/grade.   
      
   But, back to Discover as a package manager, and the management of a   
   'mix' of packages ranging from flatpaks to Snaps to conventional, in   
   this case .deb/s.   
      
   As a general rule, whenever I boot a .deb distro (or even a .rpm which   
   uses synaptic), my preferred package manager is synaptic, mixed in w/   
   sometimes my just using apt command.   
      
   Some distro/s don't even install synaptic by default, such as the   
   current KDE Neon, which is the OT.  But, if the user 'wants' to be in   
   tune w/ the available packages, synaptic can't get the job done when it   
   comes to Snap and flatpak, not can apt, of course.   
      
   So, if one is going to have to *depend* on Discover to give a full   
   picture of the available packages, I believe that it is obligated to let   
   the user configure it in a lot of different ways, for example so that it   
   only shows packages which are .deb/s, if that is desired, or .deb/s +   
   flatpaks or .deb/s + Snaps or debs + 'everything' or whatever.   
      
   I don't think the Discover interface should be confusing or inflexible.   
      
      
   --   
   Mike Easter   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca