this post was submitted on 25 Sep 2023
1140 points (92.3% liked)

linuxmemes

20880 readers
3 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
 

Re-creation of someone else's post because the original was removed and I found it funny when I first saw it

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 21 points 1 year ago (3 children)

Appimage, Snap, Flatpak, Docker, Podman, Distrobox, Toolbox...

[–] [email protected] 10 points 1 year ago (1 children)

All potentially fantastic ideas had the original author bothered to package in any of those formats. Much more common is the only release is a .deb built for an ancient version of Ubuntu, leading to my above frustrstions.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)
  1. Stop bothering with dead software.
  2. You can repackage old FOSS source code into any of those containers and install and use it that way. Nothing is stopping you, the tools are free and widely documented. You don't need to own the FOSS repository to repackage it, and actually a huge chunk of containers are packaged by people not affiliated with the development project of the software.
[–] [email protected] 1 points 1 year ago

I think we will become better served over time by using systems like the AUR or nix as it seems quite straightforward to make new software available with them. Both of those systems define the method a package should be built with, so even if the maintainer is long gone and the package hasn't been updated in a long time it will probably still be possible to build, or any changes needed to build it can be easily shared to save other people troubleshooting effort.

The drawbacks are: nix doesn't seem to have an elegant way to define that users or groups should be created (e.g. at least one package providing locate requires that) (though it does have at least one non-elegant way and one manual but less non-elegant way), and a package usable with pacman has lacked a definition of what version of every dependency it requires in at least one case where it would have been useful to me (even though that is possible apparently), so if anything made a backwards-incompatible change you may not be able to use the package manager alone to troubleshoot.

[–] [email protected] 9 points 1 year ago (1 children)

AppImage has definitely made my life a lot easier in several cases!

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

I've had poor luck with AppImage. Because of how it works, it has failed in the exact thing it was supposed to do, just werk everywhere. But I've heard it generally works well.

[–] [email protected] 1 points 1 year ago (2 children)

Those are fairly recent solutions

[–] [email protected] 4 points 1 year ago (1 children)

We only use software that has existed before the past decade in this household!

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

I wonder if someone is packaging that stuff for the new solutions

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)

I mean not really, Appimage has been around since 2004, flatpak/docker for about a decade now. But at any rate I don't see your point, the person I replied to said it's hard to run old applications on Linux and I gave him solutions on how to do that. What does their age have to do with anything?

[–] [email protected] 0 points 1 year ago (1 children)

I don’t see your point, the person I replied to said it’s hard to run old applications on Linux and I gave him solutions on how to do that. What does their age have to do with anything?

it’s hard to run old applications on Linux

What does their age have to do with anything

I'm not sure if you're taking the piss but since those solutions are so recent, you won't find old applications packaged with those solutions.

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (1 children)

They don't need to be packaged at the time of creation anyway, they can be packaged right now. Distrobox makes this easy, like let's say you need an application that only works on Ubuntu 18.04. It's two commands:

distrobox create --image ubuntu:18.04 ubuntu

distrobox enter ubuntu -- sudo apt-get install _package_

Then to export the package to your desktop you can even do

distrobox enter ubuntu -- distrobox export --app _application_

Boom, you have an Ubuntu 18.04 application on an OS of your choosing. You can theoretically do this with any distro, distrobox can use any OCI images from docker-hub, quay.io, or any registry of your choice.

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

I wouldn't exactly call that easy, but compared to how it used to be, fair enough.