XPost: comp.os.linux.advocacy   
   From: nuh-uh@nope.com   
      
   On 2026-01-21 16:21, CrudeSausage wrote:   
   > On Wed, 21 Jan 2026 18:51:12 -0500, Chris Ahlstrom wrote:   
   >   
   >> Alan wrote this post by blinking in Morse code:   
   >>   
   >>> On 2026-01-21 09:10, CrudeSausage wrote:   
   >>>> On Tue, 20 Jan 2026 20:28:27 +0000, vallor wrote:   
   >>>>   
   >>>>> At Tue, 20 Jan 2026 12:19:28 -0800, Alan  wrote:   
   >>>>>   
   >>>>>> On 2026-01-20 12:14, vallor wrote:   
   >>>>>>> At Tue, 20 Jan 2026 10:23:37 -0800, Alan  wrote:   
   >>>>>>>   
   >>>>>>>> On 2026-01-20 09:47, CrudeSausage wrote:   
   >>>>>>>>> On Tue, 20 Jan 2026 16:39:27 +0000, vallor wrote:   
   >>>>>>>>>   
   >>>>>>>>>> So say you side-load a Mac app.	You usually get a .dmg   
   > which you   
   >>>>>>>>>> mount, then drag the app folder on top of the handy alias for   
   >>>>>>>>>> the system app folders.   
   >>>>>>>>>>   
   >>>>>>>>>> That's fine, but what if you want to uninstall?	There   
   > doesn't   
   >>>>>>>>>> seem to be much of a package manager involved.   
   >>>>>>>>>>   
   >>>>>>>>>> But on Linux, apps are in packages that are tracked by the   
   >>>>>>>>>> system.   
   >>>>>>>>>> When you uninstall an app on Linux, the default is to take away   
   >>>>>>>>>> the app without touching config files -- but with the apt/dpkg   
   >>>>>>>>>> "purge" option, the package system will clean out the config   
   >>>>>>>>>> files, too.   
   >>>>>>>>>>   
   >>>>>>>>>> (Not user dot-files though, those are yours to keep.)   
   >>>>>>>>>   
   >>>>>>>>> Generally, even after I purge an application in Linux, its   
   >>>>>>>>> settings remain. You have to manually delete the folder in   
   >>>>>>>>> .config the same way you would in any other operating system. Of   
   >>>>>>>>> course, it's a lot easier to do on Linux since those folders are   
   >>>>>>>>> exactly where you would expect them to be, not lost in the   
   >>>>>>>>> registry or some obscure folder.   
   >>>>>>>>   
   >>>>>>>> LOL!   
   >>>>>>>>   
   >>>>>>>> Riiiiiiiight.   
   >>>>>>>>   
   >>>>>>>> What is "obscure" about the folders used in macOS?   
   >>>>>>>>   
   >>>>>>>> Like so many do, you confuse what you are not USED TO with   
   >>>>>>>> something being wrong.   
   >>>>>>>   
   >>>>>>> You forget that I have a Mac Studio, and it is running Tahoe. BTW,   
   >>>>>>> the 64GB and Apple M2 Ultra processor, coupled with the extra   
   >>>>>>> storage, as well as the Studio monitor, ended up north of $7K to   
   >>>>>>> purchase in the Apple store.  (I justified the expense by thinking   
   >>>>>>> of it as a Unix workstation -- which it ultimately is.)   
   >>>>>>>   
   >>>>>>> Anyhow:  On Linux, apt/dpkg (and dnf/rpm) keep track of what has   
   >>>>>>> been installed -- each and every file.   
   >>>>>>   
   >>>>>> And apps on the Mac keep all of their functional parts within the   
   >>>>>> app package.   
   >>>>>   
   >>>>> But not their config files, according to   
   >>>>>   
   >>>>> <696fe2ea$1$22$882e4bbb@reader.netnews.com>   
   >>>>   
   >>>> This is what I meant by "obscure folder."   
   >>>>   
   >>>> < snip >   
   >>>   
   >>> ~/Library/ is "obscure" to you?   
   >>   
   >> It is until you know about it :-D   
   >   
   > Maybe I didn't get the chance to know about it because my computer   
   > committed suicide as a result of me using the NVMe too much. Anal sees   
   > that as a feature.   
   Says the "man" who hides behind his killfile.   
      
   :-)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)