this post was submitted on 10 Feb 2024
496 points (94.9% liked)

Linux

48145 readers
907 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

Related Communities

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

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
496
New to Linux? Ubuntu Isn’t Your Only Option (www.howtogeek.com)
submitted 9 months ago by Ninjazzon@infosec.pub to c/linux@lemmy.ml
242 comments fedilink hide all child comments
 

Ubuntu's popularity often makes it the default choice for new Linux users. But there are tons of other Linux operating systems that deserve your attention. As such, I've highlighted some Ubuntu alternatives so you can choose based on your needs and requirements—because conformity is boring.

you are viewing a single comment's thread
view the rest of the comments
[–] cbarrick@lemmy.world 4 points 9 months ago

Sure, but the interface is probably just as important as the actual logic behind it, isn't it?

The logic is why I love Apt. Most robust dependency resolution algorithms I've used.

But also, I don't have any issues with the CLI. Having a distinction between apt-get and apt-cache and apt-mark doesn't feel weird to me. You're practically just separating the top-level sub commands by a dash instead of a space. The apt command is really just a convenience thing, and there are specialized tools for the more advanced things. Which is fine by me.

Also, the top level apt command doesn't guarantee a stable CLI, so for scripting you're supposed to use apt-get and friends anyway.

Honestly I would consider that one of the fundamental things a package manager must do.

You'd be surprised. Homebrew (the de facto standard package manager for macOS) doesn't do this. Though, you can at least lookup the "leaf" packages which are not dependencies of any other package.

And, most language-specific package managers can't do this. E.g. if you install software with pip or cargo.

you have to remember the extra step after it's finished installing

If the package is in use, it shouldn't be an orphan.

For example, what if you race with a cleanup job that is removing orphans? (Debian is hyper stable, so I often enable unattended upgrades with autoremove. I'm not so comfortable doing that on Arch ;)

What you've described is just an apt-get install when you start and and apt-get remove when you're done. Or more properly setting it as a build dependency in your source package, to let Apt handle it.

But also, why uninstall build tools?

This, at least version constraints, is another one I'd consider essential tbh. The rest are great though, I agree.

Yeah, version constraints are common. But most other package managers bail with an error when they encounter a conflict. Apt is really good about solving conflicts and proposing solutions. Often it will propose multiple solutions to your conflict for you to choose from.

Again, it's the solver part of Apt that makes it the best IMO.