Is there a good framework for making generic Linux installers?

Question

linux

As you know, for the most part, Linux applications are distributed through distributions and installed using package managers. But this is not always convenient. Sometimes you just want to dump the application into a subdirectory in /opt, create a .desktop file in /usr/share/applications and use it, and not bother with dependencies and other offal. Yes, it doesn’t sound very nice, but sometimes it’s really the most rational solution. I wonder if there are any auxiliary tools for automating the implementation of this approach - something like NSIS for Windows or the like. It is also interesting whether there are projects to implement a Mac-like application system (when archives with them are simply added by the user to a special folder) for Linux. Thanks in advance.

Answer 1

It is not necessary to drag mastdaischina in Linux.

Answer 2

As you know, for the most part, Linux applications are distributed through repositories and installed using package managers. And it's always convenient.

I fixed it.
In fact, the package manager does the same thing as NSIS, only more correctly.
Well, what's stopping you from downloading the archives of the programs you need from turnips and storing them if you need to? I don’t understand why you need all this hemorrhoids when the package manager does all this for you.

Answer 3

Something like NSIS under Windows exists precisely because under Windows there is no normal, convenient and fully compliant application installer.
Under Linux, such an installer is a harmonious part of the system itself.
Therefore, do not invent unnecessary bicycles, but rather learn how to assemble DEB and RPM. Well, and create a publicly accessible repository. For example, Oracle does just that.

Answer 4

Once upon a time, 20-25 years ago, in UNIX, and in Linux in particular, there was such a way to "fill" projects, it was called "unzipping from the root" (in some rudimentary operating systems like Minix 3 it is still preserved).
Then all UNIX-likes (Solaris, NetBSD, Linux, ...) created their own repository systems.
And now you have set a goal to go back 25 years.
Yes, for this method, the customer will simply kill you! ;-)
PS It has already been said here more than once: when moving from Windows, do not drag Windows habits with you, but take it and study how it is done in Linux.

Answer 5

The application is built for version 1.2.8 of some library and you suggest just throwing it into a directory on the system where the same library is version 1.2.3? Won't take off. Carry with you a complete set of all the necessary libraries? So this half of the system will have to be carried. Static linking? Unless, but executable files from dubious sources are not the best solution.
In Windows, everyone has system libraries, the application may not carry them. But even there there may be options when it uses an API that is not on part of the systems.