So many applications put huge cache or even machine-specific things in them. We don't use them anymore, it caused too much trouble. Exactly Richard 12 you must add steps to the uninstall to remove files created after the install. Unlike most I have to bother. You can do that on Linux. SRPMs include the upstream source, but you could easily exclude that and download from upstream with spectool, before building into the binary RPMs needed.
Snaps are a spin-off of the Ubuntu Phone project. They were the app format for the planned phone app store. Ubuntu Phone was abandoned although it lives on unofficially not because of any technical issues. Canonical came to realize that the real barriers to market entry were the business partnerships that were required with critical app vendors Facebook, Twitter, and the like and the lack of negotiating leverage that a small vendor had with them.
The Snap format was then resurrected and repurposed to solve a different issue, which was the widespread use of PPAs as a distribution format, something they were never intended for but which application makers were doing anyway.
Ubuntu resolved this by steering PPA users to Snap instead. As a result it's been a while since I've seen anyone instructing people to "install this PPA to get my application". I don't think that Snaps will ever replace normal debs for most applications, nor are they intended to. They are however intended to provide a viable option to developers who want complete control over their application packaging and deployment, such as proprietary game developers or Firefox.
They also let people publish their own apps that haven't made it through the long process involved in getting into the Debian repos. The reason that the project to develop a Snap store independent of Ubuntu's died was due to lack of interest. They realized that without a centralized search, rating, and recommendation system there wasn't a good way for people to find Snaps unless they were already really popular, and if they were already really popular then the distro was probably packaging them through the regular means anyway.
Thanks for the historical racconto. I agree with you, what's wrong with. Deb packages? They create a dependable build chain, declare their dependencies in a clear way, minimize downloads and disk usage, and most of the folk building apps know the way to deliver a functional installer in the format.
If anything, RedHat diehards have issues bringing newer versions of apps to their side, but Debian users are familiar with alien and how to de-rpm a YUM package. But as others have said before me, the real cancer of the Linux desktop is gnome.
A lot of the so-called "standards" not even honored by the gnome team these overlaying package managers are trying to adhere to stem from gnome and it's ridiculously eccentric principles. I'm still holding a candle to Budgie desktop, although after re-merging with the Solus project they have been silent.
Snaps solve a particular set of problems. If these problems aren't ones that you have, then Snap isn't something you personally need. How to create a package that works across multiple distros and multiple distro releases without going through the time and effort of creating and testing multiple different combinations of dependencies. How to release a package that doesn't have to be released in sync with each distro you support but instead is. How as a user to be able to download and run a package that you are fairly confident has limited ability to access resources on your PC that it shouldn't have access to.
Examples here being proprietary games. The main target for Snap is proprietary software and software that is released on Linux but whose major market is Windows. For the average person using Linux on their desktop or running a web or mail server their really isn't any advantage. However, not every available feature has to be a feature that you will personally use provided someone else has a use for it. I have some VMs set up to test software and always uninstall Snap because I need to control the update process since I roll back the VM before each test.
It's not a problem, as you can uninstall Snap just like you uninstall any other default package that you don't need. For a few releases Ubuntu packaged the calculator as an example of a snap. It instead ended up being a good example of why everything shouldn't be a snap. It was very slow on start up, due to having to drag its own chain of dependencies with it. I used to uninstall the default version and re-install the non-Snap version whereupon it would load almost instantly.
They ended up binning the Snap version as it was a poor advertisement for Snap. And that's the problem, isn't it? Because you end up with outdated, buggy and vulnerable libraries which only get "updated on a schedule that suits the developer" of an application, not when the maintainers of the libraries decide it needs done. Furthermore, you don't need to wait for the next distro release if you really want a newer version of your app. We'll usually package stuff soon after it is released.
You can then grab it from the development repos, with no guarantee of consistency with other things you have installed. Jumping the gun may prove problematic, too, as newer versions have a disturbing tendency to break things that depends on older, now-deprecated behavior.
Given the choice, I say let the developer who at least knows what versions of what they're using say when. I enthusiastically share your intense dislike for gnome but I'm not sure how that is germane to a discussion about package management, which occurs on an entirely different level.
Please could you clarify? See a comment on the installers thread, above this one. Forced updates and no way to hold back an update. Too bad! Another was supposed to use OpenGL but was unable to successfully do so. And this was Snaps made by Canonical on Ubuntu made by Canonical , so forget using it on some other distro if it's that screwy on the primary distro. Sounds like, from a practical matter, it's essentially running a parallel package manager -- the FlatPak depends on other FlatPaks to provide base libs.
I mean, if it works maybe that's OK but it sounds like it could get a bit out of control pretty easily. I ran an app or two as an AppImage, and that actually did work OK. They don't get cutesy with sandboxing, just blob up the libs and junk into a. AppImage file. To be honest the only one I've tried is rpcs3 PS3 emulator , but it acts just like a "portable" Windows app If you want a newer version, download the newer.
AppImage and run that instead. But I've seen plenty of complaints about this format too, since just like FlatPak and Snap it's including libs that are already on your system,. Primary complaint being apps that should match your desktop theme may not since the AppImage will be looking for whatever theme it may have within the AppImage file itself.
I've also heard these are all a bit of a PITA to package, to the point that some people "drank the Koolaid" and thought they should definitely ship an AppImage, FlatPak, or Snap, but could not sort out how to get their package to do so. Apparently this is not a terribly easy process.
I can live with the duplication. When trying to install new software such as VLC, for example onto an older - stable - system, you'll find that it won't work due to unmet dependencies.
The joke is on you. Why I am migrating back to Slackware after years of using all of the others. Sure, I occasionally have to drag an app through the seven circles of dependency hell, but for the most part, it is just:.
If not, perhaps it would be more helpful if you explicitly listed the ones you have experience with and the extent thereof. Must come from the same shop as "I could care less" which also makes no sense in the context in which it is usually used. The point, in the Linux context, is that developers keep reinventing the wheel because they can't be arsed to learn an existing toolset or believe that they have found a new and superior approach which justifies throwing out all the work that other developers have done.
Can we drop this "reinventing the wheel is a waste of time" trope, please? Reinventing the wheel is how you get better wheels. You know that gag about how we went to the moon in but we didn't have wheels on suitcases until ?
That's because wheels weren't up to the job. Materials have advanced. Manufacturing has advanced. And that let us invent new types of wheel.
If you don't like reinventing the wheel, then go back to cutting the end off a log when you need to drive somewhere. It just puzzles me that it seems to say the exact opposite of what is actually meant. Just like the other quoted example. Perhaps it would be better to have said "always invented here". At least that would make some sense.
Seems clear enough to me. I've always read it as, "Not Invented Here. In other words professional ego either individual or at the institution level won't allow me to acknowledge that someone else did a good enough job and so I will reinvent what they did, with a slight twist which enables me to claim that I'm not simply copying. I'll write my own instead. Sad that ROX never made it to the bigtime.
The "Not invented here" turning of backs was deafening. Thanks for the history, I have used Rox filer for a long time, preferred file manager and desktop skin usually over jwm, light and fast. Why would you consider anything but the best when it comes to something as critical as recovery equipment? When you simply want the best, look no further than Warn. Since Warn has been providing the most reliable winches and recovery gear. Wilderness Racks For most 4WD vehicles.
The best quality safari racks with great accessories. The beefiest racks on the market, made with the true offroading outdoorsman in mind. Click on the picture for more info. Differential Guards Think of these as a protective "cup" for your axles. Don't run around naked on the trail. Click on the pic for info on our great and growing selection of rock guards. Available for many vehicles and a favorite of Jeep owners. Amazon and Facebook are both down in that time, and Google is treading water.
Given its growth rate and prospects, Apple is already practically a value stock. Apple does, however, have problems. A woman who organized the movement says she was fired for doing so. And the U. Inflation and supply chains will be a challenge for Apple, as they will be for every manufacturer. But Apple is addressing all of those issues. If Apple is overvalued, everything is overvalued. Jeep Grand Cherokee WK Jeep Grand Cherokee WK and newer. Jeep Wrangler YJ thru Jeep Libertys Kits available for Jeep Cherokee XJ Jeep Comanche pickup, MJ.
Jeep Patriot. Jeep Commander. Toyota 4runner, Toyota 4runner Toyota FJ Cruiser. Toyota Tacoma Extra-cab, Toyota Pickup Ext cab Toyota series Landcruiser. Tacomas Toyota T Tacoma Double-cab. Toyota Tundra CrewMax. Tundra Crew Cab. Hummer H3. Hummer H2. Hummer H3T. Nissan Frontier Crewcab and up. Nissan Xterra All years. Nissan Pathfinder and up. Nissan Pathfinder Isuzu Vehicross VX.
Isuzu Trooper Isuzu Rodeo Suzuki SX4. Geo Tracker. Suzuki Equator. Ford Ranger Land Rover Discovery
0コメント