Linux

48008 readers

862 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

Seeing more projects omitting installation instructions for debian/ubuntu. (lemmy.ml)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

32 comments fedilink hide all child comments

I know there are ways to install software outside of aptitude on debian/ubuntu, (add repo, or build, or download binary, or possibly flatpak/snap/etc).

But being able to download *.deb files was one of the nicest aspect of using a debian based distros and now I'm seeing more and more projects include all distros except deb files.

Someone correct me but I vaguely recall that distributing debs is no longer recommended by debian itself?

Am I wrong, and have I only co-incidentally stumbled on projects that don't distribute debs?
I am right and this seems like a mis-step, removing one of the most beginner friendly features that helped propagate debian based distros?

Flamesuit on.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 16 points 1 year ago

I believe that deb packages should be first-class citizens in every project that distributes binaries since Debian and its derivatives have the largest user base in the Linux ecosystem.

I have mixed feelings for containerized applications since everything depends on your actual use case.

Containers were first used by sysadmins to improve a system's security through isolation of apps and services. This is of little concern to most end users.
Then came the developers who started using containers to streamline the deployment of apps and their respective dependencies. Again, this is hardly an end user scenario.
Finally, the light bulb moment: Containers can also be distributed to end users in the form of Flatpaks, Snaps, Appimages, etc.

They can be run like regular apps, with the inherited benefits I've described above (isolation + inclusion of dependencies). So, what could go wrong?

These benefits come at a cost:

Isolation: clunky system integration (wrong themes, missing icons, inaccesible files). These can be fixed, of course, but not everyone wants to be bothered with additional tinkering.
Dependencies: Having redundant libraries and/or additional runtimes in your hd may be a deal breaker for some, but I suspect less technically inclined users won't mind the overhead.

I still love the idea of a distro-agnostic package format, but in the end, the issues I've previously described, add unnecessary complexity to the user experience. This is why I don't think native packages are going away anytime soon.